grant/standards
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

handoff: suggest a next-session opener in the final report

Browse Source 
Pair the existing /compact keep-alive line with a paste-able opener for a
fresh context window. Constrained to a pointer into AGENTS.md Current state,
not a state payload, so it stays safe to lose.
This commit is contained in:
Keysat
2026-06-17 08:14:01 -05:00
parent 9031281cd4
commit e2377f4c8c
1 changed files with 9 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
guides/handoff.md
+9 -2
View File
@@ -46,5 +46,12 @@ and why. The user may provide optional focus notes; weave them in where relevant
Reply with a short summary: what got committed or pushed, what went into durable knowledge Reply with a short summary: what got committed or pushed, what went into durable knowledge
versus Current state, and anything still unresolved. If everything is clean, say it's safe versus Current state, and anything still unresolved. If everything is clean, say it's safe
to exit. Then, in case the user decides to keep the session alive instead, give them a to exit. Then give the user two ways to carry the thread forward, labelled:
one-line `/compact Focus on ...` command tailored to what matters most from this session.
- **Keep this session:** a one-line `/compact Focus on ...` command tailored to what matters
most from this session.
- **Start fresh:** a paste-able opener for the next session's first message — a *pointer, not
a payload*. Name the one thing to pick up and where it stands (e.g. "Resume the Case B
design backfill, pick up at Phase D reconcile"), and trust AGENTS.md Current state — which a
fresh session already loads — for the rest. It must be safe to lose: never carry state in the
opener that isn't already on disk.