Work with Work Threads

A Work Thread is the durable record for one piece of work. It holds the task, its current state, and the evidence gathered while working on it. It is separate from older stored history. An agent session is one run of Claude Code, Codex, or OpenCode. A session can contain more than one episode when you clearly switch to a new task. Each episode keeps the captured work and evidence for that part of the session.

Create a task

termyte task create \
  --repo github.com/acme/app \
  --title "Fix login redirect" \
  --objective "Return users to the page they requested"

The result includes an ID and version.

Add a step

termyte task add-step \
  --task <task-id> \
  --title "Add the failing redirect test" \
  --position 1 \
  --version <current-version> \
  --verification "Targeted test passes"

Each successful change increments the version. If another process changed the Work Thread first, Termyte rejects the older version without changing anything.

Inspect current state

termyte task show --task <task-id>

The output includes requirements, ordered steps, decisions, failures, checkpoints, drift, and the immediate next action.

Verify a step

termyte task verify-step \
  --task <task-id> \
  --step <step-id> \
  --version <current-version> \
  --confirm yes

Verification requires a clear confirmation from you. An agent cannot mark its own step as verified through the task service. The CLI records your confirmation as passing evidence, then verifies the step.

The CLI exposes task creation, steps, verification, checkpoints, resume, and handoff. Requirements, decisions, and failures are stored by the task service but do not yet have dedicated public CLI commands.

Daily Work

Integrations

Work Threads and verification

Work with Work Threads

Create a task

Add a step

Inspect current state

Verify a step

​Work with Work Threads

​Create a task

​Add a step

​Inspect current state

​Verify a step

Work with Work Threads

Create a task

Add a step

Inspect current state

Verify a step