gemini-cli-extensions / gemini-cli-extensions/conductor
conductor dead end with abstract path variables
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
i manage a conductor branch with a few different translations and quota realities ---
The Universal File Resolution Protocol from upstream is indeed problematic for your multi-agent architecture:
Disjoint contexts can't coordinate - If Agent A resolves "Product Definition" to one path and Agent B to another, you have a race condition
Your hardcoded paths are actually better for multi-platform - conductor/product.md is unambiguous across Claude, Copilot, Gemini, Antigravity
The index.md indirection adds failure modes - What if the index is malformed? What if agents parse it differently?
I don't see this as a wise evolution
cheers!
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
The issue mentions conductor/product.md and index.md but does not identify implementation files, tests, or an entry point. Start by locating how these paths are resolved and compare the current hardcoded-path behavior with the proposed indirection; done requires an agreed design and acceptance criteria, which the issue does not provide.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100