Sessions and recovery
Sessions are workspace-scoped durable histories. Recovery uses admitted turns, checkpoint evidence, and tool boundaries rather than assuming a prompt ran.
Inspect a session
gaionix-coder session list --workspace .
gaionix-coder session show SESSION_ID --workspace .The CLI stores sessions locally under a workspace-derived directory. --storage-root is an advanced override; use a disposable root for tests. A process lock prevents two live runtimes from claiming the same store. The VS Code extension and CLI do not automatically share a conversation or credential store.
Restore accepted context
Recovery restores admitted turn history and valid context checkpoints. A newer valid checkpoint can supersede earlier context; later admitted turns append afterward. Malformed checkpoints cannot erase the prior valid context. Merely persisting a user message does not establish runtime acceptance.
Handle UNKNOWN deliberately
UNKNOWN means acceptance or execution cannot be established. A missing Queue item is not proof of non-execution. Do not auto-retry uncertain submissions. In VS Code, explicit local archival retains UNKNOWN and the historical evidence. It does not cancel work, mark it failed, or prove it never ran.
Persistence limits
The release has deterministic session and normal restoration coverage. Do not interpret these checks as a guarantee for every power-loss, filesystem, or hardware failure. Back up important workspace data and review external side effects after interruption.