claude-code - 💡(How to fix) Fix [FEATURE] Open Editor for proposed changes [1 comments, 2 participants]

Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Problem Statement

When I am working through a conversational interface, I often find it difficult to access the ephemeral patch that Claude Code proposes, and explaining in text what I would like to comment or change can be difficult. Currently I have a workaround of asking Claude to write to a scratch space and then prompt me with vim commands to open its temporary files, but this is not reliable as Claude will commonly try to use edit functionality despite my directives. When it does work it is far more efficient than trying to explain verbally, though.

Proposed Solution

Claude Code should have a feature, perhaps Propose(), similar to Edit() or Write(), that launches the editor (similar to Ctrl-G) with a proposed edit or write. Then, you can use the editor to make changes or suggestions or ask questions in-line, which would greatly improve efficiency.

Alternative Solutions

No response

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

1. I ask Claude to write me a hello, world program.
2. It writes a hello, world patch that will just say hello, world, and I see it inline.
3. I notice that there are two issues: (a) I would like for it to use the $USER environment variable, which I already know how to plumb in, and (b) it has made a minor stylistic change I don't like.
4. As-is, I would have to verbally describe placement etc. or allow the write and then make those comments. With my proposed changes, instead it would be in an active editor window and I can just dump those inline immediately. We can then iterate conversationally, with Claude adding context as needed in the editor as well as the conversation.

Additional Context

No response