You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The thread right sidebar can hold multiple tabs but can display only one panel at a time. Users cannot keep complementary context—such as a diff, terminal, browser, and file preview—visible together inside the sidebar, resize those regions, or preserve that arrangement across wide and compact layouts.
Applies to wide desktop layouts and compact responsive drawer behavior
Gap exists on main before 065902ab76895c7384bb8e4fabd1ead234bed8c2
Steps to reproduce
Open two or more right-sidebar tabs in a thread.
Try to place the active tab left, right, above, or below another sidebar tab.
Try to resize, recombine, full-screen, restore, and retain that split between wide and compact layouts.
Expected vs actual
Expected: the sidebar can persist a split tree, align tab headers with pane bodies, target the focused pane for add-tab actions, and show one active drawer on compact viewports without discarding the saved wide layout.
Actual: the sidebar exposes one unsplit active tab surface.
Not split-thread layout: this subdivides one thread's secondary panel.
No exact open or closed issue matched the sidebar split scope, PR URL, or originating thread.
Suggested priority and effort
Medium priority, high effort: materially improves multi-context workflows but touches persistent layout, geometry, browser/terminal ownership, desktop IPC, responsive behavior, and recovery states.
Summary
The thread right sidebar can hold multiple tabs but can display only one panel at a time. Users cannot keep complementary context—such as a diff, terminal, browser, and file preview—visible together inside the sidebar, resize those regions, or preserve that arrangement across wide and compact layouts.
Implementation: PR #1601
Versions and environment
mainbefore065902ab76895c7384bb8e4fabd1ead234bed8c2Steps to reproduce
Expected vs actual
Expected: the sidebar can persist a split tree, align tab headers with pane bodies, target the focused pane for add-tab actions, and show one active drawer on compact viewports without discarding the saved wide layout.
Actual: the sidebar exposes one unsplit active tab surface.
Evidence
What you ruled out
Suggested priority and effort
Medium priority, high effort: materially improves multi-context workflows but touches persistent layout, geometry, browser/terminal ownership, desktop IPC, responsive behavior, and recovery states.
Originating implementation thread: thr_4rr623umv4