Why Coding-Agent Memory Is Not Enough: Agents Also Need Durable Task State

The real failure

The failure was not that an agent forgot a useful fact. A session ended in the middle of work, and the next session could not reliably tell the difference between what had been discussed, what had been attempted, and what had actually been verified.

A transcript contained the conversation. A summary described the broad outcome. Neither was authoritative for the questions that mattered: which step was active, which requirement was incomplete, which files changed, which checks passed, and what the next agent should do first.

Historical memory versus current state

Historical memory answers questions such as how a bug was fixed before or why a repository convention exists. Current task state answers different questions: what the active objective is, which step is pending, what evidence supports verification, and what checkpoint the next agent should use.

Memories are supplemental. Authoritative task state is primary when a task is active. This prevents a relevant historical memory from overruling the current plan.

The Termyte architecture

1. A task has an objective, requirements, and ordered steps.
2. Decisions, failures, checkpoints, and verification evidence are recorded against that task.
3. Updates use an expected version, so stale writes can be rejected.
4. Resume packets compile current state and account for workspace drift.
5. Handoffs persist the state needed by another supported agent.
6. Historical memories can add context, but do not replace task state.

The important design choice is the boundary between what happened before and what is true now.

A real handoff

Claude Code can create and checkpoint a task before handing it to Codex:

termyte task create --repo my-project --title "Finish authentication migration" --objective "Move authentication to the new provider and verify the production path"
termyte task checkpoint --task TASK_ID --workspace C:\work\my-project --platform claude-code
termyte task handoff --task TASK_ID --source claude-code --target codex --workspace C:\work\my-project

Codex can start by compiling current state:

termyte task resume --task TASK_ID --workspace C:\work\my-project

Codex still has to do the work. Termyte does not pretend a handoff is completion; it makes the starting state explicit.

Honest limitations

Termyte only knows activity captured through a configured integration. Workspace drift can still require human judgment. A checkpoint records a state; it does not freeze the repository. A handoff transfers task information, not the previous agent's full capability or context window.

The point is not perfect continuity. The point is to stop treating a transcript, a summary, and a current task plan as interchangeable.