memory-persistence

Save session context by generating a context snapshot that records current progress and Git status, storing it as a markdown file. You can then restore this state later to resume work seamlessly in a new session.

The best way to checkpoint work progress before session termination is to capture a persistent snapshot of your current state and Git status, ensuring no progress is lost when starting a new session or terminating unexpectedly.

Yes, session context persistence automatically captures Git status and workspace changes when generating a context snapshot, ensuring accurate restores and seamless resumption of your prior work state.

To resume a long-running task after an interruption, load a previously saved session snapshot to restore the exact workspace state, enabling mid-session resumption without losing prior progress.

Session checkpoint files are stored as markdown snapshots under the .cursor/tmp/ directory, providing a persistent record of your workspace state that can be accessed for later restoration.

You should avoid using session context snapshots if your workflow lacks a Git repository, as the persistence mechanism specifically records Git status and workspace changes to accurately restore your prior state.