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

Please, allow the directory where conductor stores files to be configurable.

Open
#117 0 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
cli, tooling

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.

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.

Dominant language
Python
Stars
3.7k
Forks
297
Avg merge
9m
Merged PRs (30d)
1

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.