Support Claude Code Agent Teams in split-pane display mode

[syncroswitch]

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?

current configuration for agent teams allows for
{ "teammateMode": "in-process" } or "split-panes"
but split-panes requires iterm2 or tmux.

Warps native split pane option would be significantly better.

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

No response

Additional context

No response

Operating system (OS)

macOS

How important is this feature to you?

4

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

None

[oz-for-oss]

@syncroswitch

You can view the triage session on Warp.

Here's what I found while triaging this issue:

This looks like a valid feature gap: Warp has native split panes, but Claude Code Agent Teams split-pane mode currently expects tmux or iTerm2 rather than Warp panes.

I have a few follow-up questions before I can narrow this down:

1. When you use this in Warp, are you launching Claude Code directly in a terminal pane, through Warp's Claude/Oz agent harness, or another wrapper?
2. For the desired UX, should Warp automatically create one native split per Claude teammate in the current tab, or would a Warp-provided tmux-compatible shim/CLI workflow be acceptable?

Reply in-thread with those details and the triage workflow will automatically re-evaluate the issue and update the diagnosis, labels, and next steps.

Maintainer details

I concluded that feature request to let Claude Code Agent Teams use Warp's native split panes instead of requiring tmux or iTerm2 for split-pane teammate display..

Initial triage

Classification

Enhancement request for Claude Code Agent Teams to use Warp's native split panes for teammate display.

What the report says

The reporter notes that Claude Code Agent Teams support teammateMode values such as in-process and split-pane behavior, but split-pane display currently depends on tmux or iTerm2. They would prefer Warp's built-in split panes on macOS.

Evidence from code/docs

• Claude Code's public Agent Teams docs describe split-pane mode as requiring tmux or iTerm2 with the it2 CLI, while in-process works in any terminal.
• In this repo, app/src/ai/agent_sdk/driver/harness/claude_code.rs builds and runs a single claude CLI command for the Claude harness.
• app/src/pane_group/mod.rs implements Warp native pane creation, split, focus, and resize behavior.
• I did not find a Warp-specific teammateMode, Agent Teams backend, or tmux/iTerm2 compatibility layer that would let Claude Code create Warp panes for teammates today.

Likely implementation area

This likely spans the Claude Code third-party harness (app/src/ai/agent_sdk/driver/harness/claude_code.rs, app/src/ai/agent_sdk/driver/harness/mod.rs, app/src/ai/agent_sdk/driver.rs) and native pane/session management (app/src/pane_group/mod.rs). Depending on the chosen product direction, it may also require a Warp CLI or compatibility shim surface in crates/warp_cli/src/agent.rs.

Reproducibility

Medium for the feature gap: the desired behavior is clear and current docs/code point to unsupported native Warp-pane integration, but the report does not include exact Warp/Claude Code versions or how Claude Code is launched from Warp.

Duplicate check

No duplicate was identified from the provided recent/open issue list.

Follow-up needed

Two details would help scope this correctly:

1. When you use this in Warp, are you launching Claude Code directly in a terminal pane, through Warp's Claude/Oz agent harness, or another wrapper?
2. For the desired UX, should Warp automatically create one native split per Claude teammate in the current tab, or would a Warp-provided tmux-compatible shim/CLI workflow be acceptable?

Question reasoning

1. When you use this in Warp, are you launching Claude Code directly in a terminal pane, through Warp's Claude/Oz agent harness, or another wrapper? — The launch path determines whether this should be scoped to regular terminal sessions, Warp's Claude harness, or a separate wrapper/CLI integration.
2. For the desired UX, should Warp automatically create one native split per Claude teammate in the current tab, or would a Warp-provided tmux-compatible shim/CLI workflow be acceptable? — The answer materially changes the product and implementation direction for integrating Claude Code's teammate pane backend with Warp.

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

Powered by Oz

[syncroswitch]

When you use this in Warp, are you launching Claude Code directly in a terminal pane, through Warp's Claude/Oz agent harness, or another wrapper?

directly in Warp, with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS enabled in settings and one multi agent team per tab or per window.

For the desired UX, should Warp automatically create one native split per Claude teammate in the current tab, or would a Warp-provided tmux-compatible shim/CLI workflow be acceptable?

I would strongly prefer warp native splits, one per team member.

[oz-for-oss]

@syncroswitch

You can view the triage session on Warp.

Here's what I found while triaging this issue:

Thanks for clarifying the workflow. This looks like a feature request for Warp-native Claude Code Agent Teams splits rather than a bug in Warp's existing pane UI; Claude Code's current split-pane mode is documented around tmux/iTerm2, so Warp would need a new native integration or compatibility layer.

Maintainer details

I concluded that enhancement request to let Claude Code Agent Teams launched directly in Warp use Warp-native split panes, one teammate per pane, instead of relying on in-process mode, tmux, or iTerm2..

Automated triage

Classification: Enhancement request

Summary: The request is for Claude Code Agent Teams, launched directly in Warp with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS enabled, to create one Warp-native split pane per teammate. The reporter clarified that a tmux-compatible shim would be less desirable than true Warp native splits.

Evidence reviewed:

• The reporter clarified the launch path is directly in Warp, not through Warp's Oz/Claude harness, and that the desired UX is one native split per team member.
• Claude Code's Agent Teams documentation describes in-process as the universal mode and split panes as requiring tmux or iTerm2 with the it2 CLI.
• Repository search did not find direct handling for teammateMode or CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS. Warp currently detects Claude Code as a CLI agent in app/src/terminal/cli_agent.rs, while native split-pane creation and hidden Warp child-agent panes live under app/src/pane_group/.

Likely implementation area: A bridge between Claude Code's external teammate display backend and Warp's native pane APIs. This could mean a first-class Claude Code/Warp integration or a compatibility layer that exposes pane creation, focus, and command delivery semantics to Claude Code, depending on product and upstream constraints.

Reproducibility: Medium. The feature gap is well-defined and externally documented, but exact Warp/Claude Code versions and a captured run were not provided.

Duplicates: No likely duplicate was found among the provided recent/open Warp issues; none of the candidates describe Claude Code Agent Teams using Warp native panes.

Suggested owners: @zachbai for CLI-agent/agent integration context and @vkodithala for native pane lifecycle and split layout behavior.

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

Powered by Oz