aget-save-state

To save workflow state, you create timestamped YAML checkpoint files that capture your session file path, current focus, active tasks, and artifacts. This enables reliable resume and recovery for long-running or interruptible sessions without reestablishing context.

You need session checkpoints before context-intensive operations, major refactors, or anticipated session interruptions. Creating checkpoints at natural breakpoints externalizes your current focus and active tasks, preventing context loss mid-flow.

To resume a session, you load a previously generated checkpoint file containing the session file path, active tasks, and a human-readable resume prompt. This structured YAML state capture allows agents and humans to pick up work instantly.

The checkpoint YAML capture explicitly excludes sensitive credentials to enforce safety governance. However, it does include uncommitted git status, modified artifacts, and pending questions to provide complete workflow context for recovery.

The best way to structure state persistence is using ISO 8601 timestamped YAML files stored in a dedicated sessions/checkpoints directory. This approach enforces sanitization of names and overwrite semantics for identifiable, reliable resumes.

Yes, you can use sanitized, human-friendly names to create identifiable checkpoints instead of relying solely on automatic timestamps. This allows for easier identification when you need to resume work from a specific project phase.