The console and the naetive command

Last reviewed: 28 Oct 2026

Two small things the installer puts on your machine.

The console

The console is a small program that runs on your computer (port 4000) and powers the Chats page: when you start an agent there, the console runs the real process locally and streams it to your browser. You only need it for Chats; connecting a chat agent does not.

The installer starts it. To start or restart it yourself (Connect shows the right one for your machine):

macOS, Linux, WSL:

~/.naetive/start-console.sh
~/.naetive/start-console.sh --restart
~/.naetive/start-console.sh --stop
~/.naetive/start-console.sh --keep-running
~/.naetive/start-console.sh --no-keep-running

Windows (PowerShell):

& "$env:USERPROFILE\.naetive\start-console.cmd"
& "$env:USERPROFILE\.naetive\start-console.cmd" --restart
& "$env:USERPROFILE\.naetive\start-console.cmd" --stop

Plain start leaves a console that is already running alone. --restart replaces it, for example after this computer gets a new key: the console holds the key it started with. On macOS, Linux and WSL the plain start notices a changed key on its own and restarts. --stop ends it, and the chats it was running, which you need before uninstalling: the installer runs the console in the background, so there is no window to close.

--keep-running has the computer start the console when you log in and bring it back after a crash; a deliberate --stop stays stopped. The installer turns it on (macOS, Linux with a systemd user session, and Windows), unless you turned it off. --no-keep-running turns it off and stops the console. On WSL there is no login service for this; the installer instead adds a shortcut that starts Naetive when you log in to Windows (see start-all.sh below). On Linux without a systemd user session it is not available, and says so.

Everything at once: start-all.sh

On macOS, Linux and WSL, ~/.naetive/start-all.sh starts whatever of Naetive is not running: the tunnel (only when this computer shares a project) and the console. It is safe to run twice.

~/.naetive/start-all.sh
~/.naetive/start-all.sh --status
~/.naetive/start-all.sh --no-login-start

--status and --no-login-start are for WSL: the first says whether Naetive starts when you log in to Windows, the second removes that shortcut.

The console reports in to Naetive every minute while it runs; that is what Connect's Console on means. It binds to your own machine only and answers only to the platform that installed it, so nothing else on your network can reach it.

The naetive command

Your key is read from where the installer put it, never from the command line. The project name is the part after /p/ in the Naetive address bar.

Command	What it does
`naetive status`	What runs on this computer: the console, the tunnel, the command's version, and whether Naetive starts by itself at login. It says running only for this install's own console and tunnel.
`naetive fix`	Checks this computer's key with Naetive and restarts whatever of Naetive stopped, one line per part. It never makes a new key: a refused key means approving the computer again on Connect.
`naetive share --project <name>`	Shares a project's folder with your agents from this computer; it finds the folder itself. Name the folder first if it cannot (`naetive share <folder> --project <name>`); `--create` makes an empty one for a project with no code yet.
`naetive unshare <name>`	Stops sharing it. A running tunnel stops serving it within seconds.
`naetive shares`	Lists what this computer shares, and whether running commands is on.
`naetive commands on` / `off` / `status`	Lets agents run commands on this computer, as you. On asks, and you confirm in your browser; off works at once.
`naetive link <name>`	Links this folder to a project, on this computer only. A link is a label, not access.
`naetive which`	Prints the project this folder is linked to.
`naetive export [--project <name>] [--dry-run]`	Run inside a repository to write its `.naetive` folder from the committed understanding. See The folder.
`naetive update`	Brings the command and its Claude Code hooks up to date now. It also happens by itself, at most every six hours.

naetive help lists them. On Windows without WSL, the command has export, link, which, share, unshare, shares and commands.

Where things live

~/.naetive/ (~\.naetive\ on Windows): the console, the tunnel and its launcher, the hooks, and the files behind the naetive command. The command itself is at ~/.local/bin/naetive (Windows: ~\.naetive\bin\naetive.cmd).
~/.claude/: your key file, readable only by you; Claude Code's own settings, where the installer registered the hooks; and the uninstaller.
A repository's .naetive/ folder, when you asked for it.

Nothing here needs reading; it is for when you want to know where a thing is.

Removing it

Removing Naetive from a computer has the exact steps. In short: stop the tunnel and the console, then run the uninstaller the installer left next to your key file. Your projects and their understanding live on Naetive and are untouched; Claude Code and Node are left alone.