Skip to content

Global extension policy breaks default Plan Mode temp folder behavior #156

@rodrigost23

Description

@rodrigost23

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:

  1. It dumps an unwanted conductor folder into standard projects (not setup with conductor) when I just want a basic, ephemeral plan.
  2. 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_plan tool 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions