> ## Documentation Index
> Fetch the complete documentation index at: https://docs.prbe.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Status line

> A one-line indicator in Claude Code showing whether this session is tracked.

```bash theme={null}
npx probe-research install
```

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.

| Shows | Means |
| - | - |
| `● tracking` | Recording, and nothing is filed in a project yet |
| `● tracking → folding` | Recording, against the `folding` project |
| `● tracking → folding · running` | Recording, and a run is currently open |
| `● read-only` | `/probe read`: searches work, nothing is recorded |
| `● off` | `/probe off`: no Probe calls at all |

Where [the Probe daemon](/agents/daemon.md) 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.

```bash theme={null}
probe statusline status      # whether it is installed, and what else shares the slot
probe statusline show        # print the segment this session would render right now
```

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.

> [!TIP]
>
> 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

```text theme={null}
/probe on
```

```bash theme={null}
probe session track                    # this conversation
probe session default on               # what new sessions on this computer start at
```

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`](/agents/probe-config): folder defaults (`--folder`) are retired.

See [the switch](/agents/overview.md#the-switch).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.