Skip to main content
The wizard’s Install adds a Probe segment under Claude Code’s input box, so you can see at a glance whether what you are doing is being recorded. Uninstall removes it again. Where the Probe daemon records, the words say so: on (daemon) → folding, on (daemon degraded) while the daemon is not recording for the session, read only (daemon), or on (daemon) · paused: not ML when it paused itself in a session that is not ML work. After /probe inline it reads on (inline) → folding. When the session’s transcript is not being captured, the line adds · not capturing session transcript: and the reason. The work still lands; the conversation does not.

​
It keeps what you already had

Installing wraps an existing status line rather than replacing it. If you already have one configured, it keeps running and the Probe segment is chained after it.
Uninstalling Probe removes the segment and restores exactly what it wrapped. status prints the settings file it wrote to, the command it installed, and what it chained after — which is the thing to read when two tools are competing for the slot.

​
Why it is worth installing

The expensive failure is not “tracking was off”. It is “tracking was off and nobody noticed for three weeks”. A session that is recording nothing looks exactly like a session that is recording everything, right up until you go looking for the run.
If the indicator says read-only or off and you expected otherwise, probe session status gives the full decision — which default applied, what the machine default is, and whether the capture daemon is actually running.

​
Changing what it reports

The wizard’s Defaults → Probe in new sessions (npx probe-research) sets the same default. To keep a folder out of Probe, use .probe.config: folder defaults (--folder) are retired. See the switch.