Activity from Claude Code: what is reported, and how to switch it off

Last reviewed: 16 Sep 2026

When you install Claude Code through Connect, a small hook reports what each window does, so Work can show it live and the understanding folder in your repositories can keep itself current. This page is what it reports and how to turn it off, per folder or altogether.

What the hook does

After Claude Code runs a tool (editing a file, running a command, reading a file), the hook sends Naetive the tool's name, the file path or command, and a short snippet of the result, tagged with the window it came from. That is what makes a window show as live now on Work with the files it touched. A second hook refreshes the .naetive folder when the understanding changes and catches it up when a session starts, in repositories that have the folder.

It reads only what Claude Code already handed it. It does not scan your disk.

Where it is on by default

Everywhere on the machine, once the installer has run, for every Claude Code window. There is no per-project setup.

Windows: the hooks are not installed yet; Claude Code connects and works, but its live activity and the automatic folder refresh are missing. WSL users get them by running the macOS and Linux installer inside WSL.

Switch it off for one folder

In any folder you do not want reported:

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

The hooks stay silent there; not even file paths are sent. Delete the file to switch back on.

Switch it off altogether

Remove the Naetive hooks from Claude Code's settings (~/.claude/settings.json): Claude Code stays connected and you lose only the live activity and the folder refresh. The uninstaller from Connect goes further: it removes everything the installer put on the machine, including the connection itself.

Chat agents

ChatGPT, Claude on the web and Codex have no hook. What they do through Naetive is recorded when they call it; there is nothing on your machine to switch off. Not connecting them is the opt-out.

Privacy

Everything the hook sends goes to your own Naetive account over an authenticated connection. You can regenerate your key on Connect at any time; the old key stops working immediately, though a tunnel already running keeps its own session for up to half an hour.