Group vertical tabs by project or repo root

[rgatx]

Problem

When vertical tabs are enabled, sessions from the same project can be scattered across the tab list. This makes it harder to scan active work, especially when several tabs or panes belong to the same repository or working directory.

Desired behavior

Add an optional setting to group vertical tabs by detected project root. When enabled, Warp should render lightweight project section headers in the vertical tabs list, using the detected git repo root when available and falling back to the tab working directory.

Unknown tabs should remain independent rather than all collapsing into one "Other" group.

Scope

• Vertical tabs only.
• Default off.
• Works in Tabs and Panes display modes.
• Uses detected git repo roots when available.
• Falls back to cwd/path.
• Handles Windows drive paths and WSL /mnt/<drive>/... normalization.
• Preserves existing tab and pane colors.
• Keeps drag/drop behavior predictable.

Non-goals

• Collapsible groups.
• Explicit multi-root Project Workspaces.
• Per-project settings.
• CLI agent identity/icon fixes.

@oss-maintainers I have a focused implementation ready for this. Would you prefer this to go through a spec PR first, or is this small enough to mark ready-to-implement?

[oz-for-oss]

@rgatx

Here's what I found while triaging this issue:

This looks like a well-scoped vertical-tabs enhancement, and I did not find an exact duplicate. A maintainer should still decide whether the project section-header UX and drag/drop behavior need a spec before implementation.

Maintainer details

I concluded that feature request to add optional repo/project-root section grouping to the vertical tabs panel..

Triage

This is a feature request for optional project-root grouping in the vertical tabs panel. It is primarily in the window/tab/pane surface, with a settings component because the requested behavior is default-off and user-configurable.

Current code context

• app/src/workspace/view/vertical_tabs.rs builds the vertical tab panel from workspace.tabs and renders each existing tab group in order for both Panes and Tabs display granularity.
• app/src/workspace/tab_settings.rs defines vertical-tabs settings for enabled state, display granularity, tab item mode, view mode, primary info, compact subtitle, PR links, diff stats, and details-on-hover, but not project grouping.
• app/src/terminal/view/tab_metadata.rs and app/src/terminal/view.rs expose display working directory, git branch, and detected repo path metadata that could inform a grouping key, but that metadata is not currently used to insert project section headers or reorder/group vertical-tab rows.

Duplicate check

I checked all open non-PR issues and recently closed issues from the last 7 days. The closest related requests are broader user-defined/collapsible tab groups or project workspace models, which differ from this issue's automatic repo-root section headers and explicit non-goals, so I am not marking this as a duplicate.

Follow-up

No reporter follow-up is needed for initial triage. The remaining decision is maintainer/product judgment: whether the section-header UX and drag/drop semantics should go through a spec before implementation.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz