Title: Feature Request — Reverse Branching: In-Place Archival for Long-Running Conversations
I would like a feature called Reverse Branching.
Instead of branching forward into a new chat, Reverse Branching lets the user select a point in the past and move everything before that point into a titled archive. The active conversation then continues in the same Chat or Work thread.
The archived messages and attachments remain preserved and accessible as a read-only record, but no longer count toward the active conversation length limit.
This would help long-running creative, research, and technical projects avoid an unnecessary choice between:
-
keeping all old messages active until the conversation reaches a hard limit
-
starting a disconnected new chat and manually rebuilding context
This request does not require automatic summarization, semantic retrieval, cross-chat memory, or autonomous agent communication.
It only requires:
-
user-selected archival of an earlier conversation range
-
a user-provided archive title
-
preserved, read-only access to the original messages and attachments
-
exclusion of the archived range from the active conversation limit
-
continuation in the same active Chat or Work thread
The goal is simple: let an ongoing conversation periodically move its older history into an archive while preserving its current flow.