docsconnect an AI
one command signs you in, wires every AI tool on the machine, and gives the folder its own memory.
2 pages

the npx command

npx innernet is innernet on your machine in one line. It signs you in, points every AI tool it can find at your memory, and inside a repo it gives that folder a memory of its own. There is nothing to install: npx fetches the package, runs it, and forgets it.

bash
npx innernet

what one run does#

  1. Signs you in. Your browser opens, you approve, and one key is written for this machine. No key is ever pasted into a chat.
  2. Wires every AI tool it finds. It looks for the tools you actually have and writes innernet into each one's own MCP config. Tools that can only spawn a command get innernet mcp, a thin bridge to the same hosted endpoint.
  3. Connects the folder you are in. If it is a git repo, it commits a small .innernet/connection.json naming that project's memory, and netti designs the memory's shape from what the repo actually is. Because the file is committed, the link travels with the repo: a teammate clones, runs the same command, and inherits the same context map.
  4. Installs one post-commit hook. Every commit lands as a capture, the message and the diffstat, backgrounded so it can never slow a commit down.

Re-running is always safe. It re-checks, reports, and writes nothing that is already there. --dry-run shows what it would write and touches nothing.

the tools it wires#

toolwhere innernet lands
Claude Codeits own claude mcp add -s user innernet
Cursor~/.cursor/mcp.json
Windsurf~/.codeium/windsurf/mcp_config.json
Gemini CLI~/.gemini/settings.json
Continue~/.continue/config.json
OpenCode~/.config/opencode/opencode.json
VS Code (Copilot), Cline, Roo Codetheir VS Code user storage
Antigravity~/.gemini/config/plugins/innernet/
Claude Desktop, Codex CLI, Zedtheir own config, pointed at the innernet mcp bridge
ChatGPT, Claude.aiin the browser, from your connections page

A tool you install later is picked up the next time you run the command. One it does not know yet takes the URL by hand: see connect an AI.

the other commands#

commandwhat it does
innernet statuswhat is connected on this machine
innernet login / logout / whoamisign in, forget the key here, or ask who this machine is
innernet import claudeClaude Code's own memory (~/.claude/projects)
innernet import chatgpt <file>a ChatGPT export (conversations.json)
innernet import dir <path>a folder of .md / .txt notes
innernet capture "<text>"note something from a terminal or a script
innernet mcpthe stdio bridge, for tools that can only spawn a command

Flags on connect: -y accepts the defaults, --dry-run writes nothing, --no-repo leaves the current folder alone, --no-open prints the sign-in URL instead of opening a browser, and -p <dir> connects a folder other than this one.

what it never does#

  • No key in a chat. The key it writes stays on this machine, and each client still signs in through your browser over OAuth 2.1.
  • No local copy of your memory. The map lives at innernet.live; every tool reads and writes the same one, so there is nothing to sync and nothing to go stale.
  • Nothing silent. Every file it would touch is printed, and logout forgets the key here.

Wiring a single client by hand instead is one URL: connect an AI. What the tools can then do with your memory is in MCP tools.