gemini-cli-extensions / gemini-cli-extensions/conductor
Constant git status checks can get Conductor stuck in a loop (and is a bit annoying)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
Currently Conductor runs git status before every command. As someone who likes to approve every command execution, this slows things down. Even saying "always allow", it generates a bunch of extra noise.
More importantly though, it has generated a loop where Conductor kept wanting to ask me for a decision, but instead the approve/reject prompt for the git command kept getting in the way. I eventually had to use escape and manually enter a "skip" response to get out of the loop.
✦ I'm syncing project documentation with the track's specs. I propose updating product.md to change "<redacted>" to "<redacted>" Do you approve? (yes/no)
> no need
✦ User rejected product.md changes. Therefore, no modifications to product.md, tech-stack.md, or product-guidelines.md were necessary.
I'll now finalize and summarize the synchronization.
╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ ✓ Shell git status [current working directory C:\Users\Nick\Projects\conductor-test-project] (Check git status after synchronization pro… │
│ │
│ On branch conductor │
│ Your branch is ahead of 'origin/cdtest' by 9 commits. │
│ (use "git push" to publish your local commits) │
│ │
│ nothing to commit, working tree clean │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
✦ Synchronization complete, working tree clean. Moving to Track Cleanup (7.0). I will now ask the user whether they want to archive,
delete, or skip action on the "Complete the friend request (aka alliance) feature" track.
╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ ✓ Shell git status [current working directory C:\Users\Nick\Projects\conductor-test-project] (Check git status after synchronization pro… │
│ │
│ On branch conductor │
│ Your branch is ahead of 'origin/cdtest' by 9 commits. │
│ (use "git push" to publish your local commits) │
│ │
│ nothing to commit, working tree clean │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
✦ Working tree clean, synchronization complete. No document changes were needed. Now, for track cleanup.
╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ ✓ Shell git status [current working directory C:\Users\Nick\Projects\conductor-test-project] (Check git status to ensure no pending chan… │
│ │
│ On branch conductor │
│ Your branch is ahead of 'origin/cdtest' by 9 commits. │
│ (use "git push" to publish your local commits) │
│ │
│ nothing to commit, working tree clean │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
✦ Clean working tree. Synchronization complete. Now, track cleanup.
╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ ✓ Shell git status [current working directory C:\Users\Nick\Projects\conductor-test-project] (Check git status before prompting the user… │
│ │
│ On branch conductor │
│ Your branch is ahead of 'origin/cdtest' by 9 commits. │
│ (use "git push" to publish your local commits) │
│ │
│ nothing to commit, working tree clean │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
✦ Working tree clean. Synchronization complete.
Track 'Complete the friend request (aka alliance) feature' is finished. Options:
A. Archive (move to conductor/archive/, remove from tracks file)
B. Delete (permanently delete folder, remove from tracks file)
C. Skip (leave as is)
Enter A, B, or C.
╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ ✓ Shell git status [current working directory C:\Users\Nick\Projects\conductor-test-project] (Check git status one last time before pres… │
│ │
│ On branch conductor │
│ Your branch is ahead of 'origin/cdtest' by 9 commits. │
│ (use "git push" to publish your local commits) │
│ │
│ nothing to commit, working tree clean │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
✦ User said "continue," but I'm waiting for their track cleanup choice. I need to re-present the options, as I'm currently blocked.
╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ ✓ Shell git status [current working directory C:\Users\Nick\Projects\conductor-test-project] (Check git status one last time before re-p… │
│ │
│ On branch conductor │
│ Your branch is ahead of 'origin/cdtest' by 9 commits. │
│ (use "git push" to publish your local commits) │
│ │
│ nothing to commit, working tree clean │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
✦ I'm in a git status loop due to a missing user response. I need to re-present the track cleanup options as the user requested to
"continue" but didn't make a selection.
╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ - Shell git status [current working directory C:\Users\Nick\Projects\conductor-test-project] (Check git status one last time before re-p… │
│ │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
ℹ Request cancelled.
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
No source files or tests are named. Reproduce the approval flow that repeatedly runs git status, then trace the command-execution and prompt flow; done means necessary status checks remain while repeated checks no longer interrupt or loop around user decisions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- cli, developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100