Files
pipelines/app/notes/control-tab-chat-panes.md

1.5 KiB

Ctrl+Tab chat-pane cycling

Ctrl+Tab moves forward through the open chat panes in visual tree order; Ctrl+Shift+Tab moves backward. Both wrap and focus the selected chat's composer after layout. A single open pane receives input focus without replacing it. The active Chat destination handles the chord even when its sidebar or toolbar has focus. Empty workspaces, other destinations, popup menus/dialogs and Alt/Meta-modified Tab are left alone. Command+Tab remains the OS app switcher. Existing Ctrl/Command+Shift+Arrow navigation and single-pane text selection are unchanged. Closing/cycling never sends a chat-close, interrupt or prompt request.

The handler is registered only for the ChatScreen lifetime and removed on dispose. It uses the existing workspace controller and composer focus requests; no new shell registry, server API or background polling is needed.

Checks: 16 focused ChatScreen/workspace integration tests passed through the watchdog (peak1669MB,13s). New cases cover forward/backward wrap, sidebar focus, single/empty workspaces, draft preservation, exact modifiers, popup and Search isolation. Bounded analysis is clean. Root owns combined browser acceptance.

Browser limitation: ordinary Chrome/other browsers commonly reserve physical Ctrl+Tab for switching browser tabs before web content receives it. App handling works when the host delivers the chord (including native Flutter); widget/CDP injection alone does not prove a browser will surrender its reserved shortcut. Ctrl+Shift+Arrow remains the reliable in-app web alternative.