# /exe-save

Manual escape hatch for saving a context checkpoint.

Normally you do **not** need this. Exe OS automatically creates structured
`CONTEXT CHECKPOINT` memories in the background during meaningful work, before
compaction/context pressure, and at session end. Use `/exe-save` only when the
founder explicitly says "save everything" or you want an immediate extra
checkpoint before risky manual work.

## What to save

Store a structured memory checkpoint with ALL of the following:

1. **What you accomplished** — list every completed task, fix, or deliverable
2. **Decisions made** — architectural choices, trade-offs, priorities decided
3. **Open items** — anything unfinished, blocked, or deferred
4. **Key file paths** — files you created, modified, or need to revisit
5. **Risks or concerns** — anything that might break or needs follow-up

## How to save

```bash
# Use store_memory MCP tool with a structured checkpoint
```

Call `store_memory` with this format:

```
CONTEXT CHECKPOINT [session-date]:
## Completed
- [list what was done]

## Decisions
- [list decisions and why]

## Open Items
- [list what's unfinished]

## Key Files
- [list important file paths]

## Risks
- [list concerns]
```

Then call `store_memory` again for each major decision as a separate `decision` type memory — these survive consolidation and are always retrievable via `recall_my_memory(query, retrieval_mode="decisions_only")`.

## When to use

- When the founder explicitly asks to save everything
- Before risky/manual infrastructure work where an extra checkpoint is useful
