-
Notifications
You must be signed in to change notification settings - Fork 9k
Open
Copy link
Labels
Area-UserInterfaceIssues pertaining to the user interface of the Console or TerminalIssues pertaining to the user interface of the Console or TerminalInclusionBacklogAccessibility trackingAccessibility trackingInclusionBacklog-Windows TerminalWin32Accessibility trackingAccessibility trackingIssue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.Complex enough to require an in depth planning process and actual budgeted, scheduled work.Priority-3A description (P3)A description (P3)Product-TerminalThe new Windows Terminal.The new Windows Terminal.
Milestone
Description
Feature Request: Focus Next Bell Tab
The Problem
When multiple tabs have bell indicators, there's no way to quickly navigate to them.
Windows Terminal already shows a 🔔 icon on tabs when processes output a bell character (\a). However, with many tabs open, users must visually scan all tabs to find which ones are signaling for attention.
Why This Matters: Background Processes & AI Agents
Modern terminal workflows involve running multiple background processes:
| Scenario | Bell Usage |
|---|---|
| Long-running builds | Bell on completion |
| Test suites | Bell on pass/fail |
| AI coding agents | Bell when task finishes |
| SSH sessions | Bell on disconnect/alert |
| Package installs | Bell when done |
When 3 different tabs bell while you're focused elsewhere, you need a quick way to cycle through them.
Prior Art
tmux
# Jump to window with bell
tmux select-window -t :! # Most recent belliTerm2
- Has "Jump to next bell" in menu
- Configurable keybinding
VS Code Terminal
- Bell icon clickable to focus that terminal
Proposed Solution
Add a new action focusBellTab that:
- Finds the next tab (by index) with
BellIndicator == true - Wraps around to the beginning if needed
- Cycles through on repeated presses
- Does nothing if no bells are active
Usage
// Keybinding (suggested default: Ctrl+Shift+B)
{ "keys": "ctrl+shift+b", "command": "focusBellTab" }Or via Command Palette: "Focus next bell tab"
Use Case Flow
┌─────────────────────────────────────────────────────────────┐
│ Tab 1: npm build (running) │
│ Tab 2: pytest (🔔 finished!) │
│ Tab 3: Claude Code (🔔 finished!) │
│ Tab 4: ssh server (focused) │
│ │
│ User presses Ctrl+Shift+B │
│ → Jumps to Tab 2 (first bell after current) │
│ │
│ User presses Ctrl+Shift+B again │
│ → Jumps to Tab 3 (next bell) │
│ │
│ User presses Ctrl+Shift+B again │
│ → Wraps to Tab 2 (no more bells ahead) │
└─────────────────────────────────────────────────────────────┘
Implementation
I have a working implementation ready (~40 lines of code):
- New action
FocusBellTabinAllShortcutActions.h - Handler in
AppActionHandlers.cppiterates tabs checkingTabStatus().BellIndicator() - Default keybinding
Ctrl+Shift+Bindefaults.json - Command palette entry via
Resources.resw
PR incoming - will link shortly.
Related
- Bell indicator feature already exists (just no navigation to it)
- Complements
nextTab/prevTabactions - Similar to Feature Request: Focus/Activate Tab by WT_SESSION #19783 (focus tab by session) - both improve tab navigation
Environment: Windows 11, Windows Terminal 1.21+
carlos-zamora
Metadata
Metadata
Assignees
Labels
Area-UserInterfaceIssues pertaining to the user interface of the Console or TerminalIssues pertaining to the user interface of the Console or TerminalInclusionBacklogAccessibility trackingAccessibility trackingInclusionBacklog-Windows TerminalWin32Accessibility trackingAccessibility trackingIssue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.Complex enough to require an in depth planning process and actual budgeted, scheduled work.Priority-3A description (P3)A description (P3)Product-TerminalThe new Windows Terminal.The new Windows Terminal.
Type
Projects
Status
Spec Needed ❓