Repository navigation
Sub-session visibility lost after v2.1.30 session architecture change #23894
Description
Previously, when a session went through multiple automatic context compactions, the /resume list showed these as sub-sessions (segments) under the main session entry. This was very useful for understanding session progression and jumping back to specific points in a long-running session.
Since approximately v2.1.30 (stat-based session loading), all sessions appear as a single flat entry regardless of how many compaction events occurred. While I understand this was a performance optimization (68% memory reduction), the loss of sub-session visibility is a significant UX regression for power users with long-running sessions.
Request: Restore sub-session/segment display in the /resume picker, or provide an alternative way to see compaction history within a session (e.g. expandable entries, or a --verbose flag for /resume).
Activity
scapeshift-ojones commentedon Feb 25, 2026
This is directly related to Bug 3 in #27242 — branch/sub-session navigation in the
/resumepicker is broken. I've independently confirmed that right-arrow in the picker does nothing on v2.1.50, despite branch data being perfectly preserved in the JSONL (correctparentUuidlinkage, multi-child nodes at branch points).Your report that sub-session visibility was lost after the v2.1.30 architecture change lines up with the timeline — branch navigation broke around the same timeframe (~v2.1.31).
If this is still affecting you, please 👍 and comment on #27242 where this is tracked alongside post-compaction history loss and plan-mode context severance.
mantrahq502 commentedon Feb 25, 2026
Sub-session visibility is a real operational gap. I've been using Mantra's session index as a workaround — it maintains its own view of active sessions independent of the native picker, so even when the built-in list goes stale after version bumps, you can still find and resume what you need. mantra.gonewx.com if you want to give it a try.
github-actions commentedon Mar 25, 2026
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
github-actions commentedon Apr 2, 2026
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.