What problem does this solve?
When a conversation with an agent gets long, there is no clear or discoverable way to:
- Compact the conversation — reduce context window usage by summarizing/archiving earlier messages while keeping the active session going.
- Start a new chat with the same agent — begin a fresh conversation with the same agent without the prior context.
These actions (if they exist) are not obvious in the chat UI. A user encountering a long conversation or wanting a clean slate has to guess or dig through documentation to figure out how.
What would you like to see?
- A visible "New chat" or "Start new conversation" action in the chat UI that creates a fresh conversation with the current agent.
- A visible "Compact" or "Summarize context" action that compresses the conversation history while preserving continuity.
- Both actions should be discoverable — either as buttons in the chat header, options in a chat menu, or clearly documented in the onboarding/welcome flow.
- If compaction is automatic, it should be transparent: show the user that it happened and let them access the archived portion if needed.
Anything else?
This was observed during onboarding — after a long multi-turn session, it was unclear whether starting fresh required killing the process, using a command, or if there was a UI affordance. The GSV manual mentions conversation compaction and archives but does not make it clear how a user triggers these from the chat interface.
What problem does this solve?
When a conversation with an agent gets long, there is no clear or discoverable way to:
These actions (if they exist) are not obvious in the chat UI. A user encountering a long conversation or wanting a clean slate has to guess or dig through documentation to figure out how.
What would you like to see?
Anything else?
This was observed during onboarding — after a long multi-turn session, it was unclear whether starting fresh required killing the process, using a command, or if there was a UI affordance. The GSV manual mentions conversation compaction and archives but does not make it clear how a user triggers these from the chat interface.