[FEATURE] Session title reverts to auto-generated name after context compaction

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When working on long sessions, Claude Code automatically compacts the context when the limit is reached. After compaction, any custom session title set by the user is lost and reverts to the auto-generated title from the beginning of the session. This forces users to manually rename the session again every time compaction occurs, which is disruptive when organizing multiple sessions by project or task.

Proposed Solution

The custom session title set by the user should be persisted separately from the conversation context, so it survives compaction. The title should be stored independently and never be overwritten by the auto-generated name once the user has manually renamed the session.

Alternative Solutions

Currently the only workaround is to manually rename the session again after each compaction, which is repetitive and easy to forget.

Priority

Low - Nice to have

Feature Category

Other

Use Case Example

1. I start a session and rename it to "Configurações de Ambientes e Documentação"
2. I continue working until the context is compacted automatically
3. After compaction, the session title reverts to the original auto-generated name
4. I have to rename it again — and this repeats every time compaction occurs

Additional Context

This behavior was observed in Claude Code running inside the VSCode extension.
The session title is visually reset after compaction, suggesting the title is stored
as part of the conversation context rather than as independent session metadata.

Similar tools like Cursor and other AI-powered IDEs persist session/chat titles
independently from the conversation history, which is the expected behavior for most users.