Pre-submit Checks

• I have searched Warp feature requests and there are no duplicates
• I have searched Warp docs and my feature is not there

Describe the solution you'd like?

I'd like Warp to support a Multi-root Workspace concept, similar to VS Code's "Add Folder to Workspace" feature.

1. Unified File Tree — The File Tree (Project Explorer) should display multiple root folders simultaneously, rather than being limited to a single working directory. Users can "Add Folder to Workspace" to include additional project roots.

2. Worktree-aware discovery — Since Warp already has excellent Git Worktree support, it would be natural to offer a "Add all worktrees to workspace" action that auto-discovers worktrees via git worktree list and adds them as roots in the File Tree.

3. Per-root context — Each root folder maintains its own Git status, Code Review panel, and Codebase Context indexing (which Warp already does per-worktree today). The workspace just provides a unified view on top.

4. Workspace persistence — Save/restore workspace configurations (which folders are included), similar to how Launch Configurations already save window/tab/pane layouts.

Example workflow:

git worktree add ../my-repo-feature-a feature-a
git worktree add ../my-repo-hotfix hotfix-b

Then in Warp: right-click File Tree → "Add Folder to Workspace" → the File Tree shows:

WORKSPACE
├── my-repo (main)
├── my-repo-feature-a (feature-a)
└── my-repo-hotfix (hotfix-b)

Each root has its own Code Review, Git status chip, and Agent context — all visible within one window

Is your feature request related to a problem? Please describe.

I'm always frustrated when working across multiple worktrees or related projects — Warp's File Tree only shows one directory at a time. I end up either constantly switching tabs and losing track of which maps to which branch, or opening the parent directory which pollutes the File Tree with unrelated folders.

This would also benefit non-worktree use cases: monorepo sub-projects, frontend + backend in separate repos, etc.

Additional context

• VS Code reference: https://code.visualstudio.com/docs/editor/multi-root-workspaces
• Warp already has the building blocks: per-worktree Code Review, per-worktree Codebase Context indexing, Launch Configurations for layout persistence
• Could integrate with existing Launch Configurations to save workspace folder sets

Operating system (OS)

macOS

How important is this feature to you?

4

Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1

None