[FEATURE] Multi-line editing in prompt area

[bramjochems]

Feature Description

When entering a longish prompt, I would like to be able to split the instructions visually over multiple lines.

Use Case

I believe this will make it easier to work with longer prompts. Example:

Please introduce feature foo. Do this by:
1. meeting requirement bar
2. meeting requirement baz

Is for me easier to read than:

Please introduce feature foo. Do this by: 1. meeting requirement bar 2. meeting requirement baz.

Proposed Solution

I'm not sure how the prompt area is implemented under the hood, but I could image this either being a buffer that allows multiple lines to be entered (which would also allow more complex editing to be done slightly easier), or I could image that a keybind is introduced (e.g. shift enter) that causes a line break and then the possibility to continue to edit on the next line.

Alternatives Considered

When copying pasting into the windows, multi line input is supported / can be pasted into the prompt area in the claude code terminal window in neovim, so a potential alternative is to construct prompts outside of the claude code buffer and then past them into the prompt area. This is clunky though, and for longer prompts can lead to the prompt showing that n lines have been pasted, but not showing all these lines (which is useful by itself, but makes this a less desirable alternative solution for me)

[S1M0N38]

Gemini CLI (and its forks) have the following keymap:

Ctrl+X / Meta+Enter - Open input in external editor

(However, this keymap does not work when Vim mode is active. wft?). When Ctrl+x is pressed, a new tmp buffer is opened with $EDITOR . If you have configured that environment variable to be nvim, you can edit the prompt directly in nvim.

1. Open Gemini CLI

2. Press Ctrl-x

3. Edit the prompt in Neovim and save it (:wq)

4. You can now run the edited prompt.

---

An improvement over the Gemini CLI implementation would be to make use of the current nvim instance (and fall back to spawning the $EDITOR if the nvim instance is not detected).

This feature is implemented by Gemini CLI, and I'm not sure how easy it is to implement at a wrapper layer (i.e. in claudecode.nvim).

I've added this comment expanding a bit on the idea proposed by @bramjochems, providing an example of such a feature implemented in another agent CLI app.