session-memory

To persist agent memory across restarts, this Skill creates a timestamped session directory containing markdown files that capture goals, progress, and next actions, allowing another agent to recover and resume work seamlessly.

The best way to resume a coding workflow after a branch switch is to read a handoff markdown file first, then a session state file, and finally recent timeline entries to verify the next action against git context.

You create session checkpoints for long-running tasks by prompting the agent to start a new session memory checkpoint, which generates human-readable state, timeline, files, and handoff markdown records in a dedicated directory.

Yes, you can use markdown state files for agent state persistence during nontrivial edits, maintaining a timeline and session state that captures progress and goals for continuing conversations within the same repository.

You need durable session directories for development operations when work involves risky refactoring, long-running tasks, or continuing conversations that risk interruption, ensuring context survives disconnects without starting over.