Skip to main content

​
Pick up where you left off

Termyte keeps a local record of coding work. It captures what supported agents do and keeps each piece of work in a Work Thread: the task, its current state, and the evidence gathered along the way.

Keep the task clear

Keep the objective, steps, decisions, failures, and proof together in one Work Thread.

Resume safely

Compare the current Git state with the latest checkpoint before continuing.

Move between agents

Create a handoff packet for Claude Code, Codex, or OpenCode without relying on a chat transcript.

​
What happens in the background

  1. Claude Code, Codex, or OpenCode sends an event through an installed hook or plugin.
  2. Termyte removes common secret patterns and stores the event once, even if it is replayed.
  3. It records useful views of prompts, completed tools, commands, and file activity.
  4. A background worker processes the completed session and saves useful, source-linked history.
  5. When one active Work Thread exists for a repository, its current state is supplied before older context.
Everything is stored in a SQLite database under ~/.termyte by default. There is no Termyte account or hosted sync service.
Redaction catches common patterns, not every possible secret. Treat the database as sensitive. If you enable memory processing, redacted trace-derived content can be sent to the provider selected during setup.

​
Start here

Quickstart

Install Termyte, connect an agent, and check that capture works.

Supported agents

See exactly what Claude Code, Codex, and OpenCode support.

How it works

Follow an event from capture to task state and later context.

Current limits

Read what Termyte does not do yet.