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.
This is one of the few things with no wizard screen: it writes into your agent’s own settings file rather than Probe’s, so it stays an explicit command you run.
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.
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 untracked 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
See the switch. 
