When Vinci Code is interrupted — your machine sleeps, the network drops, or you close the terminal — you can resume the task safely without losing progress or accidentally replaying commands.
Check your task ID
Every Vinci Code session has a unique task ID. To find yours, run:
/task-info
You'll see the task ID and whether it's in progress, done, or waiting for input.
Resume a task
To pick up where you left off:
vinci resume <task-id>
Vinci Code will:
- Recover the state — knows exactly what files changed and what commands ran
- Verify file contents — checks current file state against the last checkpoint
- Skip already-done work — refuses to blindly replay an interrupted shell command
- Continue the plan — shows your progress and picks up at the right step
How recovery works
Vinci Code records mutation checkpoints — snapshots of file state — around every write, edit, and bash execution. If you resume:
- Changed files are verified — Vinci proves what landed on disk from the last checkpoint.
- Interrupted commands are NOT replayed — if a bash command started but didn't finish, Vinci asks instead of guessing.
- Progress is preserved — your plan, step counter, and findings all resume where they stopped.
Task completion states
Every task ends in one of four states:
- DONE — code changed and verification passed. Only achievable with explicit confirmation.
- DONE-UNVERIFIED — code changed but verification was skipped or incomplete. Flag this if something feels off.
- WAITING — Vinci needs a decision from you (e.g., "which approach should I take?").
- BLOCKED — a concrete blocker stopped progress (e.g., missing dependency, authentication required).
Undo and recover
If Vinci made changes you want to undo:
- Type
/undoto revert the last turn's file changes (no git needed). - Use
/task-infoto see recovery status and decide whether to resume or start fresh.
For full details, see the Vinci Code guide.