session-save

You save session context by writing the current state, decisions, and next steps to a per-project dossier and MEMORY.md. This preserves session history so the next session starts from context rather than a blank slate.

Preserving project observations requires updating the per-project dossier with current state and decisions before ending the work session. This synchronization ensures session history and observability are maintained across breaks.

You need to update project memory files like MEMORY.md when ending a work session, switching projects, or taking a long break. This writes current context to project memory to avoid forgotten decisions and lost progress.

Saving session context requires no external dependencies or components. It operates independently to write updates to the per-project dossier and MEMORY.md, preserving history and observability without prerequisite tools.

You keep a structured template for ongoing work by invoking a session save to write current context, next steps, and observations to the project memory. This provides a structured format to avoid forgotten decisions between sessions.

Starting a new session from zero causes problems because previous decisions, observations, and project state are lost without session memory management. Writing updates to the per-project dossier and MEMORY.md preserves history and ensures observability.