gemini-cli-extensions / gemini-cli-extensions/conductor
feature request: custom paths for 'conductor' directory
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
For my projects I'd prefer to have the 'conductor' directory at a custom location - instead of hard-coding a directory called 'conductor' I'd like to put it in a folder like ".gemini/conductor" or "agent_metadata/conductor". I might be able to do this by modifying the md files that are in the ~/.gemini/extensions/conductor subdirectory but ideally I'd like a supported mechanism to configure the path that conductor uses to store state.
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
Start by inspecting the Markdown files under ~/.gemini/extensions/conductor and identify where the directory name is assumed. Trace how Conductor currently stores state, then determine where a supported path configuration would belong. Done means users can choose a location such as .gemini/conductor or agent_metadata/conductor without editing the extension files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100