File inferencing going wrong #18434
Unanswered
vmatam-ping
asked this question in
Q&A
Replies: 1 comment
-
|
From my point of view, this sounds like the parser is treating code-like text as path references too aggressively instead of preserving literal content. If there is no setting to disable that behavior today, the most useful fix would probably be a stricter boundary between explicit file reference syntax and plain text tokens that merely resemble paths. A minimal repro with the exact prompt before and after substitution would likely make this much easier to triage. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We have built a code reviewer which is a light application build around gemini-cli. We have noticed that at times when we have text like
@params req XXXor@import 'XXX'gemini-cli is forcefully inferring file paths replacing the actual text with close to random file paths. Is there a way to disable these file inferences with an option or some hacks to work around these?Beta Was this translation helpful? Give feedback.
All reactions