Skip to content

[FEATURE]: Replace top tab bar with a sidebar session list to prevent accidental session loss #48802

Closed as duplicate

Description

@MaksimMelan
Image ## Title: Tab-based UI causes accidental session deletion

The top tab system (instead of a sidebar stack, which is standard in AI chat UIs) leads to session loss. I just lost a session while trying to switch to it — I accidentally clicked the close button (X) that appears on hover. It's extremely easy to hit the X by mistake, and then the entire long session is deleted with no way to recover it.

Suggestion: Replace the tab bar with a sidebar session list (stack), like most other AI chat interfaces use. This would prevent accidental deletions and make session management much more intuitive.

Activity

  1. github-actions commented on Sep 13, 2026

    @github-actions
    Contributor

    This issue does not fully meet our contributing guidelines.

    What needs to be fixed:

    • No issue template was used. This project requires one of three templates: Bug Report, Feature Request, or Question.
    • If this is a feature request (requesting a sidebar instead of tabs), the title should start with [FEATURE]: and include the verification checkbox confirming the feature has not been suggested before.
    • If this is a bug report (accidental session deletion via the tab close button), it should use the Bug Report template with a proper Description field and reproduction steps.

    Please edit this issue to use the appropriate template and address the above within 2 hours, or it will be automatically closed.


    This issue might be a duplicate of existing issues. Please check:

    If you believe this was flagged incorrectly, please let a maintainer know.

  2. changed the title [-]The tab system causes session loss.[/-] [+][FEATURE]: Replace top tab bar with a sidebar session list to prevent accidental session loss[/+] on Sep 13, 2026
  3. github-actions commented on Sep 13, 2026

    @github-actions
    Contributor

    Thank you for updating the issue! It now clearly describes the problem and fits the Feature Request format. The needs:compliance label has been removed.

  4. Tarquinen commented on Oct 20, 2026

    @Tarquinen
    Member

    We're tracking this in #48882, so I'm closing this as a duplicate. Please follow that issue for updates.

    — from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions