claude-code - 💡(How to fix) Fix [Feature Request] Add Vim visual mode support (v/V/Ctrl+V) to input editor [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#47738Fetched 2026-04-15 06:43:38
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
1
Timeline (top)
labeled ×3closed ×1commented ×1

Fix Action

Fix / Workaround

Bug Description Please add vim visual mode support (v / V / Ctrl+V) to the input editor. Currently there's no way to select an arbitrary range of text in vim mode. Text objects only cover structured cases (words, quotes, brackets), and the external editor workaround clears the terminal display, losing conversation context. Visual mode is a core vim workflow — without it, vim mode is significantly less usable for vim users.

RAW_BUFFERClick to expand / collapse

Bug Description Please add vim visual mode support (v / V / Ctrl+V) to the input editor. Currently there's no way to select an arbitrary range of text in vim mode. Text objects only cover structured cases (words, quotes, brackets), and the external editor workaround clears the terminal display, losing conversation context. Visual mode is a core vim workflow — without it, vim mode is significantly less usable for vim users.

Environment Info

  • Platform: darwin
  • Terminal: iTerm.app
  • Version: 2.1.105
  • Feedback ID: 8a0b196e-a105-4ca3-84ec-9280e7069696

extent analysis

TL;DR

Implementing vim visual mode support in the input editor is likely to involve adding keybindings for v, V, and Ctrl+V to enable text selection.

Guidance

  • Review the current keybindings and shortcuts in the input editor to identify potential conflicts with the proposed vim visual mode keybindings.
  • Investigate existing text selection mechanisms in the editor to determine how they can be extended or modified to support vim-style visual mode.
  • Consider the differences between character-wise, line-wise, and block-wise visual modes in vim and how they can be implemented in the input editor.
  • Look into how other editors or terminals (e.g., iTerm.app) handle vim visual mode to gather inspiration or potential solutions.

Example

No specific code example can be provided without more information about the editor's implementation, but a potential starting point could involve mapping v to a function that toggles a visual mode, allowing users to select text.

Notes

The implementation details will depend on the specific technologies and frameworks used by the input editor, which are not specified in the issue. Additionally, ensuring that the visual mode works seamlessly with other editor features, such as text objects, will be crucial.

Recommendation

Apply a workaround by implementing custom keybindings for v, V, and Ctrl+V that mimic vim's visual mode behavior, as upgrading to a fixed version is not mentioned as an option in the issue. This approach allows for a targeted solution to the specific problem of lacking vim visual mode support.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [Feature Request] Add Vim visual mode support (v/V/Ctrl+V) to input editor [1 comments, 2 participants]