Skip to content

[Feature]: Add tab system for managing multiple chat sessions #70783

@alexandre-leng

Description

@alexandre-leng

Summary

Add a tab-based navigation to allow working on multiple chat sessions at the same time.

Problem to solve

Right now the interface only let you use one chat at a time, which becomes quickly frustrating when you need to juggle between different conversations or tasks. You basically lose context or have to remember things manually, and it slow down the workflow more than it should. For users doing more advanced usage, this is clearly not enough.

Proposed solution

The idea is to introduce a simple tab system at the top of the chat view, where each session opens in its own tab. Users should be able to create new tabs, switch between them instantly and close them when not needed. Each tab would keep its own state (model, messages, tools, etc), so nothing gets mixed. The active tab should be visually clear, and ideally tabs could be reordered by drag and drop. It would also make sense to keep them after refresh, even if thats optional.

Image

Alternatives considered

Other options like a dropdown or a list in the sidebar were considered, but they don’t really solve the problem since switching is slower and less intuitive. Opening multiple windows is also not great because it breaks the main workflow and feels heavier.

Impact

This mostly affects users who run several chats in parallel, like developers or power users. The issue is pretty constant as soon as you need more than one session. It’s not just a small annoyance, it actually slow things down and make the experience less smooth overall, with more manual steps and possible confusion.

Evidence/examples

Most modern tools already use tabs for this kind of need, like browsers or IDEs such as VS Code. In the current UI, we can only see one chat session (“main”) and there’s no way to open or manage multiple ones at the same time.

Additional information

This would align the product with common UX standards and make it way more comfortable to use in real scenarios. Even a basic version of tabs would already be a big improvement.

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions