Global extension policy breaks default Plan Mode temp folder behavior
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- cli
Research direction
Start by tracing the global extension policy and the general.plan.directory configuration in a non-Conductor workspace with Conductor enabled. Reproduce the forced ./conductor/ path and verify that Plan Mode instead uses the documented temporary directory and that exit_plan completes without manual file-write approval.
Written by the indexing model from the issue text.
Description
I'm running into an issue where having the Conductor extension installed globally hijacks the /plan directory in all my workspaces, even the ones where I'm not using Conductor at all.
According to the gemini-cli documentation for the general.plan.directory configuration:
"The directory where planning artifacts are stored. If not specified, defaults to the system temporary directory." (Specifically
~/.gemini/tmp/<project>/<session-id>/plans/)
Right now, Conductor's global policy overrides this and forces the path to ./conductor/ everywhere.
The problem is twofold:
- It dumps an unwanted
conductorfolder into standard projects (not setup with conductor) when I just want a basic, ephemeral plan. - Because the plan is forced into the active project tree instead of the default temp directory, the CLI safety mechanisms kick in. I now have to manually approve file writes before the
exit_plantool can finish. This completely defeats the frictionless, read-only sandbox nature of Plan Mode.
As long as the extension is enabled, it forces plan mode to write to ./conductor/*.md to use the exit_plan_mode tool.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Getting set up
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.
More from gemini-cli-extensions/conductor
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gemini-cli-extensions/conductor#176 · 3 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
gemini-cli-extensions/conductor#72 · 1 reaction ·
-
how to: conductor plugin for development of micro-services where each service is in its own repoOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
gemini-cli-extensions/conductor#168 · 4 comments ·
All issues in gemini-cli-extensions/conductor
Similar issues
-
correction metadata
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
acl-org/acl-anthology#10104 · 1 comment ·
Maintainers usually reply within 1 day
-
bug status/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
prowler-cloud/prowler#12885 · 1 comment ·
Maintainers usually reply within 1 day
-
Bug in GaussianTailProbabilityCalibrator: running_statistics=False still uses a windowed varianceOpenbug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
selimfirat/pysad#107 ·
Maintainers usually reply within 1 day
-
bug ci-failure high priority
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vllm-project/vllm-omni#8194 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day