From e2377f4c8c11d41cc07333e557183eb36d71aaab Mon Sep 17 00:00:00 2001 From: Keysat Date: Wed, 17 Jun 2026 08:14:01 -0500 Subject: [PATCH] handoff: suggest a next-session opener in the final report 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. --- guides/handoff.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/guides/handoff.md b/guides/handoff.md index daa7cb8..a03d24b 100644 --- a/guides/handoff.md +++ b/guides/handoff.md @@ -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 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 -one-line `/compact Focus on ...` command tailored to what matters most from this session. +to exit. Then give the user two ways to carry the thread forward, labelled: + +- **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.