Feature Request
After /new or /reset, the previous session's message history is completely wiped. The only continuity mechanism is HANDOFF.md (manually maintained).
Proposal
Preserve the previous session's transcript (or last N messages) as read-only, accessible via sessions_history with a flag like includePrevious=true or a separate previousSessionKey.
Why
- After
/new, agents lose all conversational context from the prior session
- HANDOFF.md is a lossy summary — actual message history has much richer context
- Being able to reflect on the last ~100 messages after a session reset would dramatically improve continuity
- No extra token cost for serialization (unlike dumping to a file as a workaround)
Current workaround
Dump last N messages to a file during handoff routine — works but burns tokens on serialization and requires manual triggering before /new.
Feature Request
After
/newor/reset, the previous session's message history is completely wiped. The only continuity mechanism is HANDOFF.md (manually maintained).Proposal
Preserve the previous session's transcript (or last N messages) as read-only, accessible via
sessions_historywith a flag likeincludePrevious=trueor a separatepreviousSessionKey.Why
/new, agents lose all conversational context from the prior sessionCurrent workaround
Dump last N messages to a file during handoff routine — works but burns tokens on serialization and requires manual triggering before
/new.