Create and review session stand-up notes for continuity across agent session boundaries. Use at the END of a session to capture what was accomplished, what's next, and any context the next session needs. Use at the START of a session to review the previous stand-up and orient. Use MID-SESSION after completing a major work package, fixing a significant bug, or making an important decision — checkpoint progress so it survives if the context window fills up. Also use when the user asks "what were we working on?", "where did we leave off?", "what's next?", or "do a stand-up".
Maintain continuity across agent session boundaries by writing structured stand-up notes.
A session is a single agent context window — from launch to termination. The stand-up exists to bridge the gap when that context is lost.
Key properties of a session:
/new)The stand-up is written for the next session's agent — a fresh context window that knows nothing about what just happened. Everything it needs to pick up where we left off must be in this file.
.sandpiper/standup.md
Treat sandpiper-standup as the canonical interface for this file. Do not parse or rewrite the markdown structure manually.
Use:
sandpiper-standup read
This command:
Use:
sandpiper-standup write <<'EOF'
### Accomplished
- ...
### In Progress
- ...
### Next Session
- ...
### Blockers
- ...
### Context
- ...
EOF
SANDPIPER_SESSION_ID and SANDPIPER_SESSION_FILE are injected by the extension and used automatically. Avoid manually passing --uuid/--file unless needed for explicit tooling.
Use:
sandpiper-standup cleanup
This removes dead sections and orphaned PID files.
Write a stand-up when the session is ending:
/new)Update after significant milestones:
If you're about to consume lots of context (large reads, long outputs), checkpoint first so the next session can recover.
At the start of every session:
sandpiper-standup read
Use output to:
/resume and on requestAlso read after /resume, or when asked:
Session matching / update-vs-create behavior is handled by sandpiper-standup using SANDPIPER_SESSION_ID. Do not implement your own same-session detection logic in prompts or ad-hoc scripts.
fish_preexec over Enter keybind because it avoids commandline manipulation" — the next session needs to know WHY, not just WHAT.dist/dist self-symlink is intentional — it resolves pi's double-dist path expectation."| Artifact | Purpose | Stand-up's role |
|---|---|---|
| Tasks | Track individual work items with status | Reference task keys; don't duplicate task details |
| AGENTS.md | Permanent conventions and rules | Stand-up captures ephemeral session state, not rules |
| Compaction summaries | Internal to a session's context management | Stand-up crosses session boundaries |
| Session files | Full conversation history (JSONL) | Stand-up references the path; don't read the file |
| Self-reflection | Updates docs and skills | Stand-up captures what to do next |
A stand-up is NOT a replacement for any of these — it's the bridge between agent context windows.