session-autosave

Auto-save session state during refactoring by triggering automatic persistence on batch completion, test passes, or checkpoint creation, ensuring your session state is saved accordingly. This prevents work loss and enables quick recovery from interruptions.

A checkpoint registry updates and records checkpoints alongside session data for traceability. When autosave triggers, it implements /sessionwrite calls and updates the checkpoint registry, coordinating with a .sessions directory and checkpoint metadata.

Use automated session persistence in refactoring workflows that generate batches, require tests or lint/type checks to pass, or create checkpoints. It ensures the session state is saved accordingly when these specific refactor-related events occur.

Yes, session autosave aligns with context-autonomy and rollback guards to ensure safe, automatic saves. This context-aware coordination guarantees that session persistence only happens when it is safe to do so during refactoring.

Session autosave coordinates with a .sessions directory and checkpoint metadata as part of its integration. You need to ensure this directory structure is available so the /sessionwrite calls can properly persist the session state.

The best way to recover a refactoring session is relying on the autosave mechanism, which persists your session when a checkpoint is created. The checkpoint registry and .sessions directory metadata provide the traceability needed for quick recovery.