gemini-cli-extensions / gemini-cli-extensions/conductor
Please, allow the directory where conductor stores files to be configurable.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
Imagine if every extension / AI that all contributors of an OSS project use want to create a directory in the root of the project ... One will end up with a giant mess of unrelated directories cluttering the root.
I'm attempting to organize all AI clutter/slop (Gemini, Claude, others) under .agents/. Can I tell Conductor to use .agents/conductor instead ?
PS.: If this is already possible, gemini-cli didn't know about.
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
No file, test, or entry point is identified in the issue. Start by locating where Conductor chooses or creates its storage directory and how its configuration is read; done means a setting can redirect Conductor's files to .agents/conductor while preserving the current default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100