gemini-cli-extensions / gemini-cli-extensions/conductor
Allow suggesting changes without exiting the conductor flow
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
In the attached screenshot, I am being prompted to accept a code change during conductor:implement. I want to suggest a change to the generated code, but when I select "No, suggest changes (esc)", it exits conductor:implement entirely. Is there a way to adjust this flow so that I can suggest changes without having to restart /conductor:implement?
(I've also noticed that the Allow for this session approval doesn't seem to stick; I'm prompted repeatedly for every change. Why is that?)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the conductor:implement flow and the approval prompt that handles “No, suggest changes (esc)” and “Allow for this session.” Confirm how those choices affect the running flow and session approvals; done means suggested changes return to implementation and session approval is honored without repeated prompts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100