park

To save your current session context for later resumption, use the park command to store your workspace state in a local _system/parked directory with topic metadata. This enables zero-loss context retrieval when you return to the task.

Switching to a different project across sessions involves loading its status from a parked file using the resume command. This reconstructs your previous workspace state from the saved markdown metadata, enabling quick restoration of focus.

Yes, you can list all parked session notes to see available topics for resumption. The system stores each parked item as a predictive file structure in the _system/parked directory, allowing you to browse and select saved contexts.

Saving your workspace context requires no external dependencies. The system uses a local _system/parked directory with frontmatter metadata and a predictable file structure to store and reconstruct your session state internally.

You should avoid using parked session files when you need real-time cross-device synchronization, as the system relies on a local directory structure. It is designed for single-environment zero-loss resumption rather than distributed cloud-based context sharing.

To reload context across sessions after pausing work, issue a resume command with the specific topic name. This action retrieves the saved frontmatter metadata from the local parked store to reconstruct your previous working state.