gemini-cli - 💡(How to fix) Fix Gemini CLI reads setting from VS Code GCA plugin [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#25597Fetched 2026-04-18 05:57:32
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
1
Participants
Timeline (top)
labeled ×2

Root Cause

'geminidoceassist.rule': '#AXEL' word does not appear while prompting with Gemini CLI because this rule is set for VSCode GCA plugin.

RAW_BUFFERClick to expand / collapse

What happened?

bug-report-history-1776455841609.json

It seems that gemini CLI has an opened communication channel with GCA via gemini.md file. Maybe it is working as expected but it could polute the data between the user and the Gemini CLI model (instead of GCA plugin model).

In the following screencast, one can see how Gemini CLI response with a 'geminidoceassist.rule': '#AXEL' set in the open setting json format from VS Code IDE.

[ACTION REQUIRED] 📎 PLEASE ATTACH THE EXPORTED CHAT HISTORY JSON FILE TO THIS ISSUE IF YOU FEEL COMFORTABLE SHARING IT.

What did you expect to happen?

'geminidoceassist.rule': '#AXEL' word does not appear while prompting with Gemini CLI because this rule is set for VSCode GCA plugin.

Client information

  • CLI Version: 0.38.1
  • Git Commit: 7f5580034
  • Session ID: 6766a437-896e-4ab2-b227-f269d5a8cea6
  • Operating System: darwin v24.11.0
  • Sandbox Environment: no sandbox
  • Model Version: gemini-3-flash-preview
  • Auth Type: oauth-personal
  • Memory Usage: 439.4 MB
  • Terminal Name: Unknown
  • Terminal Background: #1e1e1e
  • Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

No response

extent analysis

TL;DR

The Gemini CLI may be using an incorrect model due to an open communication channel with GCA via the gemini.md file, causing unexpected responses.

Guidance

  • Verify the contents of the gemini.md file to ensure it is not causing interference with the Gemini CLI model.
  • Check the VS Code IDE settings to confirm that the 'geminidoceassist.rule': '#AXEL' setting is only applied to the GCA plugin and not the Gemini CLI.
  • Review the chat history JSON file (if shared) to identify any patterns or clues that may indicate why the Gemini CLI is responding with the GCA plugin model's rule.
  • Consider testing the Gemini CLI with a different model or settings to isolate the issue.

Example

No code snippet is provided as the issue does not contain sufficient technical details to create a relevant example.

Notes

The issue lacks specific technical details about the gemini.md file and the GCA plugin settings, making it challenging to provide a definitive solution. Further investigation and clarification are needed to determine the root cause.

Recommendation

Apply workaround: Isolate the Gemini CLI and GCA plugin settings to prevent interference and test the CLI with a different model or settings to identify the cause of the issue. This approach allows for a more controlled environment to troubleshoot the problem.

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

gemini-cli - 💡(How to fix) Fix Gemini CLI reads setting from VS Code GCA plugin [1 participants]