Skip to content

[FR] Tweak plan then continue #2886

Closed as duplicate
Closed as duplicate

Description

@lycarter

After Claude proposes a plan, it gives the user two options: "would you like to proceed?: "yes" and "no, keep planning"

It would be helpful to add a third option "add comments, then proceed", which allows me to write a few small comments, then proceed in auto-accept mode.

At the moment, my options are:

  • Press "yes", then immediately esc to interrupt, add my comment, then proceed, which is a bit annoying.
  • Press "no, keep planning", enter my comment, and wait for the entire plan to be re-generated, then press yes.

Both of those interactions add extra unnecessary tokens.

Activity

  1. sid374 commented on Jul 2, 2025

    @sid374
    Contributor

    If you hit "no" and then give it your comments, it will regenerate the plan according to your comments and continue on. i.e even if you press no, Claude can still access the plan and take your comments in stride.

  2. lycarter commented on Jul 2, 2025

    @lycarter
    Author

    That makes sense, and that's my current workaround, but it's a few extra seconds of waiting and a few extra keystrokes.

    Beyond the small time hit, my understanding is that when I press no, and it regenerates the plan, both plans need to be generated (more output tokens), and both plans wind up in context (at least, that's what it looks like visually, let me know if that's not actually what's happening).

    For example, I ask it to perform a big refactor in a FE codebase. The plan is like...60 lines long, and one block of the plan is "update import order to be less confusing" or something along those lines. The tweak I want to give is "don't bother touching the import order, just run prettier before committing and it'll auto-reorder". I would imagine that the nicely formatted plan plus my small additional comment are enough for it to proceed in auto-accept mode, without needing to regenerate a plan.

  3. sid374 commented on Jul 2, 2025

    @sid374
    Contributor

    Gotcha, if it's just a small tweak to the plan you could use realtime steering to adjust the plan after the model's started working on it. So this is what it would look like:

    1. Accept plan
    2. Type out your change and hit enter (while the Claude is doing it's thing)
    3. Message get's picked up by the model after the next tool call and it adjusts course
  4. lycarter commented on Jul 2, 2025

    @lycarter
    Author

    Will give that a shot, thanks!

  5. RomainGehrig commented on Jul 3, 2025

    @RomainGehrig

    Just to add to the conversation, it would be nice to be able to pop the plan in $EDITOR, make some changes, save and close the file. Then Claude could look at it and go with it or ask clarifications by re-issuing the plan.

    My use-case is more for longer plans around a full feature that just need some tweaks. If there are more than 2 things to change, I tend to forget what I wanted to change while typing the first few (and Claude is still pumping code in the background).

    (If the whole plan needs tweaking, I just recreate a plan with different directions.)

  6. Hyperrick commented on Jul 5, 2025

    @Hyperrick

    It would be helpful if pressing "Esc" wouldn't delete the plan from the terminal output. Then I wouldn't need to take notes..

  7. github-actions commented on Aug 16, 2025

    @github-actions

    Found 3 possible duplicate issues:

    1. [FEATURE_REQ]: Add response before embarking #4039
    2. Feature Request: Allow Final Instructions Before Plan Approval #2844
    3. Yes, and..., Yes, but... #2504

    This issue will be automatically closed as a duplicate in 3 days.

    • If your issue is a duplicate, please close it and 👍 the existing issue instead
    • To prevent auto-closure, add a comment or 👎 this comment

    🤖 Generated with Claude Code

  8. github-actions commented on Aug 20, 2025

    @github-actions

    This issue has been automatically closed as a duplicate of #4039.

    If this is incorrect, please re-open this issue or create a new one.

    🤖 Generated with Claude Code

  9. github-actions commented on Aug 27, 2025

    @github-actions

    This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

  10. locked as resolved and limited conversation to collaborators on Aug 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

duplicateThis issue or pull request already exists

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions