innernet

one memory for every AI tool.

npx innernet

That's the whole setup. It signs you in to innernet.live once, then wires every AI tool on your machine — Claude Code, Cursor, Codex, Windsurf, Gemini CLI, Claude Desktop, VS Code, Cline, Zed, OpenCode … — to the same memory over MCP. Run it inside a repo and that folder gets a memory of its own, shaped by what the repo actually is.

Every tool now reads and writes one memory. It's maintained for you — netti folds what you say into it, keeps it current, and hands each tool the slice it needs. Nothing runs a model on your machine and there is no local copy to keep in sync.

commands

| | | |---|---| | npx innernet | sign in · wire every AI tool found here · connect this folder | | innernet import claude | bring in what Claude Code already remembers (~/.claude/projects) | | innernet import chatgpt conversations.json | bring in a ChatGPT data export | | innernet import dir ./notes | bring in a folder of markdown / text | | innernet status | what's wired on this machine | | innernet mcp | the stdio bridge — for tools that can only spawn a command (written into their config for you) | | innernet login · logout · whoami | the one key this machine holds |

--dry-run shows what would be written without writing it. Re-running is always safe.

how it's wired

Tools that speak streamable-HTTP MCP get the URL directly:

https://innernet.live/api/mcp
Authorization: Bearer <your key>

Tools that only spawn commands get innernet mcp, a thin bridge that forwards to the same URL. There is one implementation, on the server; what your tools see is what it advertises, live.

ChatGPT and Claude.ai connect over OAuth from innernet.live/connectors.

for CI / scripts

Set INNERNET_API_KEY and skip the browser. Keys come from innernet login or innernet.live/account.

upgrading from the old CLI

Before 1.0, innernet kept a local copy of your memory under .innernet/ and ran its own sync agent. That's gone — the memory lives at innernet.live and every tool reads it there. Every old command still answers: innernet mcp serve is now the bridge, innernet connect / mcp install are the one command above, and the rest exit quietly so old hooks keep working. Run npx innernet in a repo that has an old .innernet/ map and it offers to move it up.

innernet.live · docs · MIT