Skip to content

CLI input should have a vi/vim input mode #13

Closed

Description

@RyanHecht

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

Activity

  1. Gelio commented on Oct 8, 2025

    @Gelio

    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?

    Gemini CLI does that and I liked that. See CTRL+X in https://github.com/google-gemini/gemini-cli/blob/main/docs/cli/keyboard-shortcuts.md

    IMO 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).

  2. hackel commented on Dec 12, 2025

    @hackel

    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!

  3. AtomicMegaNerd commented on Mar 19, 2026

    @AtomicMegaNerd

    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.

  4. ahmelkholy commented on Apr 14, 2026

    @ahmelkholy

    yes every time i hit escap key it stop it form wokring i want have such a mode vim in cli mode

  5. Ram-G commented on May 6, 2026

    @Ram-G

    This is needed, please.

  6. pjvds commented on May 7, 2026

    @pjvds

    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.

  7. karnull commented on Jun 8, 2026

    @karnull

    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

  8. austinorth commented on Aug 25, 2026

    @austinorth

    Pleeeeeease! 🙏🏻

  9. RyanHecht commented on Sep 1, 2026

    @RyanHecht
    ContributorAuthor

    Hey folks! We've shipped a vim mode in 1.0.81 -- update to the latest and try it out with /vim!

  10. cpolish commented on Sep 8, 2026

    @cpolish

    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?

  11. aidangannon commented on Sep 8, 2026

    @aidangannon

    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

  12. dsayling commented on Sep 10, 2026

    @dsayling

    /settings editorMode vim seems to be a valid setting, but the editor doesn't seem to be able to switch from insert mode to visual or normal mode 🤷

  13. pjvds commented on Sep 15, 2026

    @pjvds

    I can confirm that as per version 1.0.84-5, after setting the editorMode to vim the text input is now vim powered! This is awesome.

    To set editorMode run: /settings editorMode vim

  14. aidangannon commented on Oct 15, 2026

    @aidangannon

    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...

  15. aidangannon commented on Oct 21, 2026

    @aidangannon

    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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions