Add keyboard shortcut to cycle through orchestration subagents in a pane

[vikvang]

Summary

Add keyboard shortcuts for cycling through orchestration sessions (orchestrator + subagents) within the same pane.

Problem

When an orchestration run has multiple sessions, navigating between the orchestrator and child agent sessions currently requires leaving the keyboard flow or using broader conversation/navigation surfaces. This makes it harder to quickly check progress across active sessions while staying focused in the current pane.

Reproduction steps or desired workflow

1. Start an agent orchestration run with multiple subagents.
2. Stay in the pane that contains the orchestration session.
3. Use a keyboard shortcut to move focus to the next orchestration session in that run.
4. Optionally use a reverse shortcut to move to the previous orchestration session.

Default keybindings

• Next orchestration session: ctrl-] on macOS, Linux, and Windows.
• Previous orchestration session: ctrl-[ on macOS, Linux, and Windows.

Artifacts

None attached.

Warp version

Unknown.

Operating system

macOS.

[oz-for-oss]

@vikvang

Here's what I found while triaging this issue:

This looks like a feature gap rather than a bug: orchestration child agents can already be reached through the pill-bar UI, but there does not appear to be a keyboard command for next/previous child-agent navigation yet.

Maintainer details

I concluded that feature request to add keyboard next/previous navigation for orchestration child-agent sessions within the current pane..

Triage summary

This is an enhancement request for keyboard-first navigation between child agents in an orchestration run. The requested workflow is clear: while focused in an orchestration pane, a shortcut should move to the next child agent session, with an optional reverse shortcut for the previous child.

Current behavior from code inspection

• app/src/ai/blocklist/agent_view/orchestration_pill_bar.rs already builds the orchestration pill bar, renders child-agent pills, and handles mouse-driven pill clicks plus overflow menu actions such as opening/focusing a child agent.
• app/src/terminal/view/action.rs defines the existing orchestration navigation actions (RevealChildAgent, SwitchAgentViewToConversation, OpenChildAgentInNewPane, and related stop/kill actions).
• app/src/terminal/view.rs forwards those actions to pane-group events, and app/src/pane_group/mod.rs contains the pane swap/reveal logic for child-agent conversations.
• app/src/workspace/mod.rs and app/src/util/bindings.rs register general tab, pane, and session keybindings such as Ctrl+Tab, but I did not find a registered action for cycling within the current orchestration's child-agent list.

Likely implementation area

This likely needs a new next/previous orchestration-child navigation action that can resolve the active orchestration tree from the current agent view, pick the adjacent child conversation, and dispatch through the existing SwitchAgentViewToConversation / RevealChildAgent path. The keybinding should be added through the editable binding infrastructure with care to avoid conflicts with existing tab/session cycling shortcuts.

Duplicate search

I enumerated open non-PR issues across the repository and checked related Ctrl+Tab/session, subagent, child-agent, and orchestration navigation requests. Several issues mention adjacent areas (general Ctrl+Tab behavior or broader subagent capabilities), but none matched this specific request closely enough to mark as a duplicate.

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

Powered by Oz

[oz-for-oss]

This issue has been labeled ready-to-implement and is open for contributions involving code changes. If you'd like to tackle it, feel free to open a pull request against this issue. You can also comment @oz-agent on this issue to have the bot draft an implementation PR automatically.

[kevinchevalier]

This makes sense. Added this as ready to implement.

[oz-for-oss]

@vikvang

I'm implementing this issue with no spec context.

You can view the conversation on Warp.

I created a new draft implementation PR for this issue.

Next steps:

• Review the implementation changes in the PR.
• Complete any manual verification needed for this issue before merging.

Powered by Oz