openclaw - 💡(How to fix) Fix [Feature]: Add tab system for managing multiple chat sessions [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#70783Fetched 2026-04-24 05:53:41
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Participants
Timeline (top)
labeled ×1

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

Root Cause

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.

RAW_BUFFERClick to expand / collapse

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.

<img width="2170" height="725" alt="Image" src="https://github.com/user-attachments/assets/6610b629-4b45-49db-8a30-910e43fbc3ab" />

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.

<img width="1915" height="390" alt="Image" src="https://github.com/user-attachments/assets/df2560a5-2d5b-4c48-a409-1aed73f5a469" />

extent analysis

TL;DR

Implement a tab-based navigation system to enable multiple chat sessions simultaneously.

Guidance

  • Introduce a tab system at the top of the chat view, where each session opens in its own tab.
  • Ensure each tab maintains its own state, including model, messages, and tools.
  • Implement features to create new tabs, switch between them, and close them when not needed.
  • Consider adding drag-and-drop functionality to reorder tabs.

Example

No specific code example is provided, as the issue focuses on the conceptual implementation of a tab-based system.

Notes

The proposed solution aims to align the product with common UX standards, making it more comfortable to use in real scenarios. However, the issue lacks technical details, so a more specific implementation plan cannot be provided.

Recommendation

Apply a workaround by introducing a basic tab system, as even a minimal implementation would be a significant improvement over the current single-chat-session interface.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Feature]: Add tab system for managing multiple chat sessions [1 participants]