Skip to content
Work with your agent

Move the work to a fresh Session—without starting over.

Carry the current intent and project state into a clean coding-agent conversation. Keep every step reviewable and never confuse a generated handoff with a delivered one.

NOT THE SAME THING

Resumereopens the same host conversation.

Fresh Sessioncreates a new host conversation and binds it to the Task.

Project truthremains in Skopos and the repository.

THE HANDOFF

Six explicit steps. No invisible jump between them.

The original Session prepares and reviews the transfer. The receiving Session accepts current authority before continuing.

01 · Prepare

Confirm that a fresh Session is the right move.

Use a fresh Session when the current conversation is large enough to obscure the objective. A native resume keeps the same conversation and is a different operation.

Say this to your agent
Review the active Task and tell me whether we should continue here, resume this same chat later, or prepare a fresh Session. Explain the reason before changing ownership.
Exact command path
  1. npx skopos task show <task-id> . --json
  2. npx skopos session context . --actor <id> --session-id <origin-session-id> --host <host> --json
PROJECT TRUTHNothing moves yet. The current Task and origin Session remain authoritative.
HOST REALITY

Automation follows verified host capability.

Certified for first release

Codex

Real-host proof covers fresh Task creation, prompt injection, Session binding, and return to the originating reviewer.

Adapter available; verification planned

Claude Code

Generated lifecycle hooks exist, but the first release does not claim real-host Claude Code certification.

Exact fallback

Any manual host

Review and copy the rendered prompt, then accept it with the real receiving Session identity.

WHEN VERIFICATION STOPS

Refresh what changed. Never silently trim or guess.

  • RefreshableRebuild the handoff around its preserved capsule.
  • StaleInspect the Task-owned state before proceeding.
  • ConflictedReconcile actions, mutations, claims, or contamination.
  • InvalidReject the handoff. Sensitive values are redacted and over-budget prompts fail explicitly.
NEXT GUIDE

See the complete feature loop.

Plan and finish a feature