Keep project context across coding sessions.
The local alpha captures work from Claude Code, Codex, and OpenCode in the same SQLite database. Each agent connection has a different setup and maturity level.
Start with the agent you already use.
Termyte does not replace Claude Code, Codex, or OpenCode. It records the work around them so another session can inspect what happened and continue from a known state. The table shows what is supported today.
| Agent | Capture | Processing | Current note |
|---|---|---|---|
| Claude Code | yes | available | Captures sessions and can use its authenticated CLI for background processing. |
| Codex | yes | available | Captures sessions and can use its authenticated CLI for background processing. |
| OpenCode | yes | available | Capture and non-interactive processing use a generated local plugin; automatic context injection and complete live acceptance proof are not available yet. |
What happens after capture.
Captured activity is stored in the local runtime. From there, Termyte can support local retrieval, context selection, feedback, and task tools through its MCP server. The viewer lets you inspect the records instead of treating them as invisible prompt material.
Current boundary
OpenCode capture and non-interactive processing are supported, but automatic context injection and complete live acceptance proof are not. The alpha also has no company-source integrations or connectors yet.