Save a progress checkpoint for the active session. Use when user says "save progress", "checkpoint", "save checkpoint", "save my work", "before I stop", "ending session", "wrapping up", or at natural stopping points during implementation. Requires active feature.
Save a progress checkpoint for the active session. The checkpoint captures your current git state (branch, commit hash, dirty state) and optional notes, stored server-side for crash recovery and session continuity.
.nexus.json — confirm activeFeature is setIf $ARGUMENTS provided:
nexus save --notes "$ARGUMENTS"
Short flag: -n is equivalent to --notes.
nexus save -n "$ARGUMENTS"
If no arguments, ask the user for a brief description of current progress, then run the command.
Bare save (no notes):
nexus save
The CLI prints:
Checkpoint saved
If nothing changed since the last checkpoint:
No changes since last checkpoint
Each checkpoint stores:
This data is stored server-side and used for crash recovery — if a session is interrupted, the next engineer/agent can see exactly where work left off.
| Scenario | CLI Message | What to Tell User |
|---|---|---|
| No active feature | No active feature. Pick one first: nexus feature pick <slug> | "No active feature. Pick one first with /pick." |
| No changes since last checkpoint | No changes since last checkpoint | "Nothing new to save. This is fine — your last checkpoint is still current." |
| Not logged in | Not logged in. Run: nexus login | Run nexus login --token <key> first |
| Server error (500) | Error: <message> (500) | "Checkpoint not saved to server. Your local work is safe. Try again." |
Suggest /save at meaningful boundaries:
When NOT to suggest: Don't suggest saving after every small change. Save at meaningful boundaries, not after every file edit.
/learn/decision/done