naetive

Activity troubleshooting

Last reviewed: 16 Sep 2026

The symptoms people actually see, and the fix for each. Most of them end with "re-run the installer from Connect", which is safe to do any time: it repairs what is missing and changes nothing that works.

"My Claude Code window is not on Who's here"

  1. It has not done anything yet. A window appears when it makes its first call or edits its first file. Ask it something about the project.
  2. You are on Windows. The activity hooks are not installed there yet, so a window shows only when it calls Naetive, not when it edits files. Run the macOS and Linux installer inside WSL to get the hooks.
  3. The folder is opted out. A .claude/naetive-disabled file in the folder silences the hooks. Delete it if you did not mean it.
  4. A Claude Code update removed the hooks. Updates sometimes rewrite Claude Code's settings and drop third-party hooks. Re-run the installer; it puts them back.
  5. You regenerated your key. Everything on the machine still has the old one. Re-run the installer.

"One window shows as two rows"

A window announces itself twice (through its connection and through the hooks) and Naetive pairs the two. If they do not pair, run /mcp in that window to reconnect it; the rows fold together on the next call. If it keeps happening, re-run the installer.

"Activity stopped after it worked for days"

Almost always the settings rewrite above. Re-run the installer. If Work still shows nothing, check that Claude Code lists naetive under /mcp.

"The folder in my repo is not refreshing"

The refresh runs from the hooks, so the causes above apply. Also: the folder only refreshes in repositories that already have it. Run naetive export once in that repository to ask for it.

Still stuck?

Send this with your report; it is the full server-side picture of your connections and needs only your key, which the installer put on your machine:

curl -H "Authorization: Bearer <your key>" {{PLATFORM_URL}}/api/v2/diagnostics/me

Run it in a plain terminal, not inside an agent: printing your key into a chat is what the key guard hook exists to stop.