[FEATURE] On context continuation, file a read-only archive of conversation history
Problem Statement
When a Claude Code web session reaches its context limit and undergoes context continuation (session reset/restart), the original conversation is summarized but the full conversation history becomes inaccessible to the user. While I understand the technical necessity of context continuation and accept that the new session operates from a summary, the original conversation contained valuable information that I was using as a working notebook.
Proposed Solution
Make archived conversations available as read-only references after context continuation.
- The new session continues with a summary (current behavior - this is fine)
- The old session remains accessible in a read-only archive/history view
- User can reference the archived conversation for context, requirements, and decisions
The archived sessions would be read-only and wouldn't consume current context, but would be available for human reference.
The Claude Code web "Sessions" list has a dropdown filter menu offering "Active" and "Archived" - the conversations that hit context limit could either be filed under "Archived" or a new "Continued" option of the dropdown menu.
The footer of the archived conversation should feature a hyperlink to its continuation.
Priority
Medium - Would be very helpful
Feature Category
Other
Use Case Example
I was using the conversation as a design notebook containing:
- Feature requirements and specifications
- Design decisions and rationale
- Implementation discussions
- Future enhancement plans
Losing access to this information mid-project creates a significant documentation gap.
Having access to the conversation archive would let me keep that valuable information, even as a new conversation has begun as continuation.
Additional Context
No response