Credentials. Captured sessions can contain pasted secrets or project content, so review the privacy model before capturing sensitive projects.
Who it is forA developer who remembers an agent solved a problem last month but cannot find the session.
The problemPast agent conversations are scattered across provider logs and hard to search by topic.
The outcomeA list of matching local sessions you can open and review, with no account or network needed.
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
curl -fsSL https://app.use-habitat.com/install.sh | shto install the latest checksum-verified release. - Run
ht installto install hooks and the local background service. - Run
ht syncto reconcile provider history. - Run
ht sessions search "migration"and replace the query with your own keyword. - Run
ht sessions show SESSION_IDwith an ID from the results to inspect one session.
Prompt for your agent
In the habitat-cli repo, install HT locally, run `ht sync`, then run `ht sessions search "<keyword>"`. Expected output: a list of local sessions that match the keyword. Verify that each result includes a session ID you can pass to `ht sessions show`.
Caveat. HT is under active development and CLI changes are expected before 1.0, so re-check `ht help` after upgrades.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for wusterbuilds/habitat-cli and "Find past coding agent sessions by keyword"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer