You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature or problem you'd like to solve
The core problem is the lack of efficient, keyboard-driven navigation and editing for users familiar with modal editors (like Vim/Vi) within the interactive portions of the GitHub Copilot CLI. The feature requested is the implementation of a Vim mode to enable users to navigate, select, and edit text (e.g., suggested commands, explanations, or input prompts) using standard Vim keybindings (h, j, k, l, w, d, y, etc.) in addition to the default keybindings.
Proposed solution
We need to introduce Normal, Insert, and Visual modes to allow power users to edit and manipulate text with high speed and precision, mirroring the functionality found in other modern, interactive CLIs.
Example prompts or workflows
No response
Additional context
No response
Reacted by GyuYong Jung, Aaron Batilo, Levi Trammell, Louie Lee, Joel Långström, Aung Myo Kyaw, kalmar-akit, vorhey, Brenno Oliveira, Yuri Henrique and 66 more
Reacted by Andrew Neilson, Oliver W., Spencer Rogers, Brian DeHamer, Bernhard Breytenbach, Alexander van Noord, Andy Huynh, jaime-paredes-tala, IUAD1LV1, linus-entiros and 5 more
Reacted by Andy Huynh, jaime-paredes-tala, IUAD1LV1, linus-entiros, DiegoRenner, matt nguyen and Roland Hudák
Perhaps a simpler alternative would be to use open the prompt using $EDITOR and then after it is closed, replace the current prompt with whatever the user typed in that editor?
Basic keybindings for prompt editing would be more than sufficient, but it might be worthwhile to integrate with Neovim (like vscode-neovim), using its API to do most of the work for you. That would be rather epic!
Just basic vim motions for prompt editing would go a long way here. Claude code gets this part right. Don't need anything super comprehensive or fancy. Editing plans in the external editor already works well.
Reacted by Ram Gupta and Rodrigo Goya
Reacted by Alexander van Noord, Parker Smith, Andy Huynh, jaime-paredes-tala, Marvan-T, DiegoRenner, Krzysztof Słonka, Fernando de Oliveira, Jason Weathered and Drew Ayling
Perhaps a simpler alternative would be to use open the prompt using $EDITOR and then after it is closed, replace the current prompt with whatever the user typed in that editor?
ℹ️ this is supported for a while now with ctrl+g as default shortcut.
Reacted by Albert Zhen, Rahul Jha, Jason Weathered and leon
In interactive mode the navigation feels quite inconsistent. Some prompts let me use j/k, but others only work with the arrow keys. Bit confusing and breaks the flow a bit, would be good to have it consistent
Hey folks! We've shipped a vim mode in 1.0.81 -- update to the latest and try it out with /vim!
Hey @RyanHecht, thanks so much for this. I've tried to use /vim in my Copilot CLI installation on 1.0.83, but unfortunately, it's not recognised as a command: is there any more info on this feature?
Reacted by Chris Dunphy, Aidan Gannon and Drew Ayling
Hey @RyanHecht is this released for everyone or slowly rolled out via feature toggles or canary? I can't access it either... Doesn't seem to work with the --experimental flag either
Hey @RyanHecht is there some planned work to address the visual mode implementation? for me its pretty much unusable as it stands, one of the main features of the /vim mode in claudecode is being able to chunk delete text
Activity
Gelio commentedon Oct 8, 2025
Perhaps a simpler alternative would be to use open the prompt using
$EDITORand then after it is closed, replace the current prompt with whatever the user typed in that editor?Gemini CLI does that and I liked that. See
CTRL+Xin https://github.com/google-gemini/gemini-cli/blob/main/docs/cli/keyboard-shortcuts.mdIMO that would achieve full Vim compatibility, since users would be able to edit the prompt in a real
vim/nvim(or even use VSCode if they want to).hackel commentedon Dec 12, 2025
Basic keybindings for prompt editing would be more than sufficient, but it might be worthwhile to integrate with Neovim (like vscode-neovim), using its API to do most of the work for you. That would be rather epic!
AtomicMegaNerd commentedon Mar 19, 2026
Just basic vim motions for prompt editing would go a long way here. Claude code gets this part right. Don't need anything super comprehensive or fancy. Editing plans in the external editor already works well.
ahmelkholy commentedon Apr 14, 2026
yes every time i hit escap key it stop it form wokring i want have such a mode vim in cli mode
Ram-G commentedon May 6, 2026
This is needed, please.
pjvds commentedon May 7, 2026
ℹ️ this is supported for a while now with
ctrl+gas default shortcut.karnull commentedon Jun 8, 2026
In interactive mode the navigation feels quite inconsistent. Some prompts let me use
j/k, but others only work with the arrow keys. Bit confusing and breaks the flow a bit, would be good to have it consistentaustinorth commentedon Aug 25, 2026
Pleeeeeease! 🙏🏻
RyanHecht commentedon Sep 1, 2026
Hey folks! We've shipped a vim mode in 1.0.81 -- update to the latest and try it out with
/vim!cpolish commentedon Sep 8, 2026
Hey @RyanHecht, thanks so much for this. I've tried to use
/vimin my Copilot CLI installation on 1.0.83, but unfortunately, it's not recognised as a command: is there any more info on this feature?aidangannon commentedon Sep 8, 2026
Hey @RyanHecht is this released for everyone or slowly rolled out via feature toggles or canary? I can't access it either... Doesn't seem to work with the
--experimentalflag eitherdsayling commentedon Sep 10, 2026
/settings editorMode vimseems to be a valid setting, but the editor doesn't seem to be able to switch from insert mode to visual or normal mode 🤷pjvds commentedon Sep 15, 2026
I can confirm that as per version
1.0.84-5, after setting theeditorModetovimthe text input is now vim powered! This is awesome.To set
editorModerun:/settings editorMode vimaidangannon commentedon Oct 15, 2026
how do i go into visual mode to select and do: ESC -> b -> v -> w -> d
won't let me go into visual mode so feels like a bit of an incomplete implementation tbh...
aidangannon commentedon Oct 21, 2026
Hey @RyanHecht is there some planned work to address the visual mode implementation? for me its pretty much unusable as it stands, one of the main features of the /vim mode in claudecode is being able to chunk delete text