sync-session

To save coding session progress, you can run a session capture workflow that appends your current focus, modified files, and unresolved blockers to a SESSION.md file. This preserves your work state for seamless resumption later.

Documenting session context involves recording your completed tasks, current focus, and required follow-ups in a markdown file. This approach ensures your work state is retained, allowing you to resume efficiently in your next session.

You can track blockers and modified files by running an end-of-session workflow that collects progress, documents outstanding issues, and lists changed files. This information is appended to your project's session file for future reference.

Yes, using a markdown file to preserve session state is effective for managing work across intervals. The session file captures commands to resume work, outstanding tasks, and context, ensuring continuity across breaks.

Session capture workflows can operate without external dependencies, relying solely on your project workspace to append progress and context to a local markdown file. This ensures your work state is preserved independently.

You should run a session sync workflow at the end of a work session. It applies during end-of-session workflows to capture progress, document blockers, and list modified files, ensuring context is retained for the next session.