[DOCS] Interactive mode Vim NORMAL key table omits `/` reverse history search mapping
Documentation Type
Missing documentation (feature not documented)
Documentation Location
https://code.claude.com/docs/en/interactive-mode
Section/Topic
Vim editor mode -> Navigation (NORMAL mode)
Current Documentation
The Vim mode reference currently documents NORMAL-mode navigation keys like:
|h/j/k/l| Move left/down/up/right | |Space| Move right | |w| Next word | |e| End of word | |b| Previous word | |0| Beginning of line | |$| End of line |
The same page documents reverse history search only as a separate shortcut:
Press Ctrl+R to interactively search through your command history:
The v2.1.152 changelog says:
Vim mode: / in NORMAL mode now opens reverse history search (like Ctrl+R), matching bash/zsh vi-mode
What's Wrong or Missing?
The interactive-mode page documents Vim NORMAL-mode key mappings and documents reverse history search, but it does not connect the two by stating that pressing / in NORMAL mode opens reverse history search as of v2.1.152.
That leaves a gap for users reading the Vim key table: the changelog announces a new NORMAL-mode binding, but the reference page still only describes Ctrl+R for starting history search.
Suggested Improvement
Add / to the Vim NORMAL-mode reference in interactive-mode, near the existing Navigation or Command history content. For example:
| / | Open reverse history search |
Also mention that this invokes the same history search flow documented in the Ctrl+R section, so users understand / is the vi-mode equivalent.
Impact
Medium - Makes feature difficult to understand
Additional Context
Affected Pages:
| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/interactive-mode | 131-151, 221-236 | Vim NORMAL-mode key table lists navigation bindings, and reverse history search is documented only under Ctrl+R |
| https://code.claude.com/docs/en/terminal-config | 293-299 | Points readers to the interactive-mode Vim reference as the full key table |
Total scope: 2 pages affected
Observed against changelog entry in v2.1.152.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗