[DOCS] Agent teams docs still say `Shift+Up/Down` for teammate navigation after v2.1.47 change to `Shift+Down` wrapping
Documentation Type
Incorrect/outdated documentation
Documentation Location
https://code.claude.com/docs/en/agent-teams
Section/Topic
Teammate selection and in-process interaction keyboard guidance
Current Documentation
The page currently states Shift+Up/Down in multiple places:
- "Use Shift+Up/Down to select a teammate and message them directly"
- "In-process: ... Use Shift+Up/Down to select a teammate..."
- "In-process mode: use Shift+Up/Down to select a teammate..."
What's Wrong or Missing?
Claude Code v2.1.47 changed teammate navigation behavior:
- navigation now uses only
Shift+Down(with wrapping) - no dual
Shift+Up+Shift+Downnavigation model
The docs still describe the old key behavior, which leads to incorrect instructions for current versions.
Suggested Improvement
- Replace
Shift+Up/Downreferences withShift+Down (wraps)inagent-teams. - Add a short note describing wrap behavior (last teammate -> first teammate).
- If
Shift+Upnow has no teammate-navigation behavior, explicitly note that to avoid confusion.
Suggested wording:
In-process mode: press Shift+Down to cycle through teammates (wraps from last back to first).
Impact
Medium - Makes feature difficult to understand
Additional Context
Affected Pages:
| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/agent-teams | 81 | Intro keyboard guidance uses Shift+Up/Down |
| https://code.claude.com/docs/en/agent-teams | 93 | In-process mode section uses Shift+Up/Down |
| https://code.claude.com/docs/en/agent-teams | 153 | Direct teammate messaging section uses Shift+Up/Down |
Release note reference (v2.1.47):
- "Simplified teammate navigation to use only Shift+Down (with wrapping) instead of both Shift+Up and Shift+Down."
Dedup check:
- Open issue #26511 discusses a navigation bug side effect. This issue is specifically about versioned documentation being out of date with the released keybinding behavior.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗