Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`load_builtin_commands` warning after installing conductor

Open
#139 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
ai, cli

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.

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).

Dominant language
Python
Stars
3.8k
Forks
301
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gemini-cli-extensions/conductor

All issues in gemini-cli-extensions/conductor

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.