durable-session-state

To persist session state across compaction, save task plans, scope decisions, and validation evidence to durable project files in the .claude/session/tasks/ directory before your session compacts or restarts. This ensures long-running swarm-mode tasks retain critical context.

Stale approval detection tracks git HEAD and diff summaries at each gate approval to automatically invalidate outdated reviewer approvals when code edits occur after a session resumes. This enforces the swarm-mode contract that approvals must happen after the latest edit.

You can save task artifacts and gate approval ledgers by writing them to structured, project-local files. This automatically persists critical validation evidence and approval records, preventing re-litigated decisions and wasted rework during team handoffs.

Yes, durable session persistence is ideal for multi-phase swarm development tasks and long coding sessions. It maintains authoritative task artifacts and validation evidence across compaction, restarts, and handoffs, ensuring no completed work is lost or repeated.

Session context loss causes rework because compaction, restarts, or handoffs drop critical task plans and settled scope decisions. Without durable persistence to project files, teams face invalidated approvals and must re-litigate previously settled decisions unnecessarily.