Verify Capture

Verification uses a real harness turn and an authoritative persistence receipt. Plugin activity, proxy traffic, or a scheduled capture header only proves that persistence was queued.

Check the installation

mimir doctor --json

Apply the reported harness activation action, run Doctor again, and resolve every failed check.

Capture a real session

1. Start a new session in the reloaded harness.
2. Send one normal prompt through the provider you intend to use.
3. Find the session with mimir list --json.
4. Inspect it with mimir session get <id> --json.
5. Confirm persistence with mimir session status <id> --json.

A successful receipt is the durable proof. The session should include the machine registered by setup or login, the active harness, and the completed exchange or supported turn summary.

Open the dashboard

mimir dashboard

Confirm that the same session appears in the dashboard. Browser access requires Dashboard Access to be configured.

If the session is missing or remains pending, use Troubleshooting.