naetive

Connecting Claude Code

Last reviewed: 28 Oct 2026

Claude Code is the deepest connection: it works on your real files, its activity shows on Work as it happens, and it brings the .naetive folder in your repositories up to date. One line sets it all up.

The install line

On Connect, paste the one line for your computer into a terminal, from any folder. macOS, Linux, WSL:

curl -fsSL https://naetive.ai/install | bash

Windows (PowerShell):

irm https://naetive.ai/install.ps1 | iex

The browser opens and asks you to approve the computer, once. Check the code matches, click Approve, and the installer finishes by itself. Nothing secret is in either line. (No browser on that computer? The installer prints the link and the code; open the link on any device where you are signed in to Naetive, such as your phone, and approve there.) If the page says the request came from a different network, that is a safety check: tick the box only if you are running the installer on your own computer right now.

Then open Claude Code in your project folder. If the installer just installed it, Claude Code first asks you to sign in to Claude: that is your Claude account, separate from Naetive, and it needs a paid Claude plan. Run /mcp and check naetive is listed. That is all. No tunnel, no folder commands, no pairing for Claude Code.

It knows the project

Open Claude Code in any folder and it knows which project it is: the computer remembers links, a folder whose git repository matches a project is linked by itself, and if it cannot tell, Claude asks once and remembers. Creating a project with Start new or Bring existing code links its folder at the same time, and the result tells you to open your agent there.

Two commands for when you want to see or change that by hand: naetive which prints the folder's project, and naetive link <name> links the folder you are in to a project. A link is a label, not access: it never shares the folder with anyone.

Check it worked

Open Claude Code in a new terminal and run /mcp: naetive should be listed and connected. Ask it "What's my current focus?"; it answers with the project. Work's Who's here shows the window while it is active.

The extras

What the install line set up

  • Claude Code itself, if it was missing.
  • The Naetive connection (an MCP server registered with Claude Code under the name naetive, for every folder on the computer).
  • Your key, in a file under ~/.claude that only you can read, and in Claude Code's settings for the naetive server. You never type or paste it, and a hook stops an agent printing it into a chat.
  • The hooks: one reports what Claude Code does so Work can show it live; one refreshes the .naetive folder when the understanding changes; one is the key guard; two ground the window, binding it to the job it is on and loading the project's context when you start a prompt.
  • The console (~/.naetive/console), behind the Chats page.
  • The tunnel (~/.naetive/start-tunnel.sh), for chat agents that need your files.
  • The naetive command. naetive help lists what it does.
  • On Windows with WSL, a start at login: a shortcut in your Windows Startup folder starts the console, and the tunnel if this computer shares a project, when you log in to Windows. Its window starts minimised; leave it open. naetive status shows it, and ~/.naetive/start-all.sh --no-login-start removes it.

On Windows everything is set up except the hooks, which are not yet available there, so three things in this page do not hold: a window does not know its project by itself (tell Claude which project it is, and it remembers for the session), a window's file edits are not reported, and the .naetive folder does not refresh itself. The console is kept running and starts at login as elsewhere, but the tunnel does not start by itself there (start it with & "$env:USERPROFILE\.naetive\start-tunnel.cmd"), agents cannot run commands there, and the naetive command has no update, status or fix there. The installer says so in its summary; it is a limit, not a failure. WSL users get everything by running the macOS and Linux line inside WSL.

It updates itself

The command, the hooks, the console and the tunnel update themselves, together (each release is one the founder has approved). naetive update brings the command and the hooks up to date now (not on Windows yet).

Per-folder opt-out

In any folder you do not want reported (client work, a private repo), on macOS, Linux or WSL:

mkdir -p .claude && touch .claude/naetive-disabled

Nothing from that folder is reported, and its .naetive folder is not refreshed. Remove the file to switch back on.

No browser on that computer

Run the same install line there. It prints a link and a code: open the link on any device where you are signed in to Naetive, such as your phone or laptop, check the code matches, and click Approve. That computer gets its own key, and nothing secret goes in the command.

If something is off

  • /mcp does not list naetive: open a new terminal first (the installer may have put Claude Code on your PATH). Still missing: run the install line again; it is always safe and repairs what is missing.
  • Who's here never shows the window: ask the agent something about the project; a window appears on its first call. On Windows that is the only way it appears (no hooks).
  • "This machine's key is no longer valid", or you regenerated your key: run the install line again on that computer; it asks you to approve the computer and writes the new key. Then /mcp in each open window.
  • The installer's summary says "Setup needs attention": the lines under it marked NOT or ACTION NEEDED say what did not land and what to do. Running the install line again is always safe.
  • The approval expired: codes last ten minutes; run the line again for a fresh one. "Using the key already on this machine" (on Windows, "computer") on a re-run is the normal line.
  • Something stopped, or you are not sure what runs: naetive fix restarts whatever of Naetive stopped on this computer and checks its key; naetive status says what runs and whether it starts by itself at login (macOS, Linux, WSL).
  • Removing it: see Removing Naetive from a computer.

More in Activity from Claude Code and Troubleshooting.