gemini-cli - 💡(How to fix) Fix Allow namespacing gemini cli-specific properties in agents and skills [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#25960Fetched 2026-04-26 05:24:34
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
issue_type_added ×1labeled ×1
RAW_BUFFERClick to expand / collapse

What would you like to be added?

Every agent insists on using the flat preamble properties in agents (and skills), making them all conflict with each other. This is extremely annoying if you use multiple agents like me. It would be awesome if Junie would allow namespacing its properties in the frontmatter of agents (and ideally skills too). It could easily be optional.

Why is this needed?

It's impossible to use Gemini CLI specific agent and skill properties if you need to use them with other agents.

Additional context

No response

extent analysis

TL;DR

Implementing namespacing for properties in the frontmatter of agents and skills could resolve conflicts between multiple agents.

Guidance

  • Introduce a namespacing mechanism to allow agents and skills to have unique property identifiers, reducing conflicts.
  • Consider making namespacing optional to accommodate existing configurations.
  • Evaluate the feasibility of implementing namespacing for both agents and skills to ensure consistency.
  • Investigate potential impacts on Gemini CLI specific agent and skill properties when used with multiple agents.

Notes

The implementation details of namespacing are not specified, and the exact technical requirements are unclear.

Recommendation

Apply workaround: Implement a custom namespacing solution or wait for an official update that includes namespacing support, as it would likely resolve the conflict issue between multiple agents.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING