How to find out why agent sessions stopped capturing with Habitat CLI

Who it is forAn engineer who notices recent agent sessions are missing from HT.

The problemCapture can stop silently, leaving gaps in the session record.

The outcomeA clear health picture and repair guidance for the capture problem.

What you need first

macOS (Apple silicon or Intel) or Linux (Arm64 or x64); Windows is not currently supported
Codex or Claude Code sessions to capture
Terminal access and permission to install a local background service and provider hooks
Optional: a Habitat Cloud workspace or a self-hosted Habitat-compatible endpoint, only if you want team sharing

Steps

Run ht preflight --json for a read-only environment inspection.
Run ht status for concise capture and delivery health.
Run ht doctor for detailed diagnostics and repair guidance.
Run ht sync to reconcile provider history after fixing the issue.

Prompt for your agent

In the habitat-cli repo, run `ht preflight --json` and `ht doctor`, then summarize the findings for <PROJECT_PATH>. Expected output: a short list of problems and suggested repairs. Verify that you have not changed hooks or the service without asking the user first.

Caveat. The README says a real Codex hook must be reviewed and trusted by the user, so an agent cannot complete that step for them.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for wusterbuilds/habitat-cli and "Find out why agent sessions stopped capturing"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp