gemini-cli-extensions / gemini-cli-extensions/conductor
`load_builtin_commands` warning after installing conductor
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
After installing the Conductor extension, every time that I start Gemini CLI I get the following warning message in the Debug Console (opened with F12):
│ ℹ Authenticated via "gemini-api-key".
│ ℹ Loading extension: conductor
│ ⚠ [STARTUP] Cannot start phase 'load_builtin_commands': phase is already active. Call end()
│ before starting again.
If I disable the extension, the warning message disappears:
gemini extensions disable conductor --scope workspace
I was wondering if this warning could be hiding other misbehaviors I've been experiencing with Gemini CLI (e.g. "Allow for this session" tool usage not working).
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
Reproduce the warning by enabling the conductor extension in Gemini CLI, then inspect the startup path around the load_builtin_commands phase and the Debug Console output. Compare startup with the extension disabled and verify that the warning is gone without introducing the reported tool-usage misbehavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100