naetive

Connecting Claude Code

Last reviewed: 16 Sep 2026

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

The one-click install

On the Connect page, open the Claude Code row and click Install.

  1. A small launcher downloads. Double-click it (macOS and Linux run it in a terminal; Windows runs a PowerShell script).
  2. A tab opens in your browser asking you to approve this computer. Click Approve. If the request comes from a different network than the one you are browsing on, the page says so and asks you to confirm; that is a safety check, not an error.
  3. The installer finishes on its own. Your connection key is never shown, pasted or typed.

Prefer a terminal? The row also shows a one-line command that prints a link and a code; you approve in the browser the same way. Nothing secret is in that command.

What it sets up

  • Claude Code itself, if it is not installed.
  • The Naetive connection (an MCP server registered with Claude Code under the name naetive, for every folder on the machine).
  • Your key in a file under ~/.claude, readable only by you. Agents read it from there; nothing puts it on a command line, and a hook stops an agent from 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 and catches it up at session start; one is the key guard above; two ground the window, binding it to the job it is on and loading the project's context when you start a prompt.
  • The local console (~/.naetive/console), which powers the Chats page.
  • The tunnel (~/.naetive/start-tunnel.sh), for chat agents that need your files.
  • The naetive command (naetive export writes a repo's folder).

On Windows everything above is set up except the activity hooks, which are not yet available there. Claude Code still connects and works; its live activity and the automatic folder refresh are missing. WSL users get the hooks by running the macOS and Linux installer inside WSL.

Check it worked

Open Claude Code and run /mcp: naetive should be listed and connected. The Connect page shows the Claude Code row as set up after its first call, and Work's Who's here shows the window while it is active.

Per-folder opt-out

In any folder you do not want reported (client work, a private repo):

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

The hooks stay silent there. Remove the file to switch back on.

If something is off

  • /mcp does not list naetive: re-run the installer, or open the row's "Prefer to do it by hand?" fold for the one claude mcp add command.
  • The row says set up but Who's here never shows the window: the hooks are missing (Windows) or the key file is gone. Re-run the installer.
  • You regenerated your key: every agent stops until it has the new one. Re-run the installer; it picks the new key up.

More in Activity from Claude Code and Troubleshooting.