-
Notifications
You must be signed in to change notification settings - Fork 14.1k
[Agent] Plan Mode is to eager to start implementation #20143
Copy link
Copy link
Labels
area/coreIssues related to User Interface, OS Support, Core FunctionalityIssues related to User Interface, OS Support, Core Functionalitypriority/p1Important and should be addressed in the near term.Important and should be addressed in the near term.workstream-rollupLabel used to tag epics and features that are associated with one of the three primary workstreamsLabel used to tag epics and features that are associated with one of the three primary workstreams🔒 maintainer only⛔ Do not contribute. Internal roadmap item.⛔ Do not contribute. Internal roadmap item.
Metadata
Metadata
Assignees
Labels
area/coreIssues related to User Interface, OS Support, Core FunctionalityIssues related to User Interface, OS Support, Core Functionalitypriority/p1Important and should be addressed in the near term.Important and should be addressed in the near term.workstream-rollupLabel used to tag epics and features that are associated with one of the three primary workstreamsLabel used to tag epics and features that are associated with one of the three primary workstreams🔒 maintainer only⛔ Do not contribute. Internal roadmap item.⛔ Do not contribute. Internal roadmap item.
Type
Fields
Give feedbackNo fields configured for Task.
Projects
StatusShow more project fields
Closed
What would you like to be added?
My question: Analyze anls operators and suggest better naming.
Gemini CLI output:
I would like Plan Mode be less eager for implementation. It happens I mistakenly select "Yes.." and my source code gets changed, while I just wanted to brainstorm.
Why is this needed?
Plan Mode is great in helping me to better understand what I want by asking me questions. Yet I want to use it for brainstorming or generating analysis that I use for planning in the next, future, steps.
Additional context
No response