save-session

Session context persistence involves capturing decisions, outcomes, and file states, then writing them to a dated Markdown file. This creates a canonical snapshot that allows future sessions to resume work seamlessly without losing prior progress.

Invoke a save command to capture session context and write it to a date-stamped Markdown file in ~/.cursor/session-data. The file includes sections for What We Are Building, What Worked, What Did Not Work, Current State of Files, and Decisions Made for seamless resumption.

Save session context during end-of-work sessions or before context limits are reached. This preserves decisions, outcomes, and next steps across tasks, ensuring seamless handoffs and resumption after interruptions or context window exhaustion.

Writing a canonical, date-stamped Markdown snapshot to ~/.cursor/session-data is the best way to log session context for handoffs. This records decisions, outcomes, failures, and open questions, allowing the next session to resume with full context.

The saved session file uses Markdown format and is stored in ~/.cursor/session-data with a date-based filename like YYYY-MM-DD-<shortid>-session.tmp. It contains structured sections for What We Are Building, What Worked, What Did Not Work, Current State of Files, and Decisions Made.