You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Agents misinterpret LSP diagnostics as failed edits #9102
When an edit or write operation succeeds but triggers LSP diagnostics (errors/warnings), the tool output only shows the diagnostics. This can lead agents to believe the operation failed, causing them to retry unnecessarily or get stuck in a loop.
The output should clearly indicate that the edit/write was applied successfully, even if diagnostics are present.
It sounds a bit like a bad model issue. Had zero problems with that. Tool calls show clearly successful, agent interprets the type errors correctly, also understands when it's not due to that edit. What model are you using?
Don't have transcripts at hand but I'm pretty sure Gemini 3 Pro and Codex 5.2 both at max thinking levels showed such behavior.
And even if this is a matter of weak model - why not help it? This case is a free lunch to me in this regard
Activity
github-actions commentedon Jan 17, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
pschiel commentedon Jan 17, 2026
It sounds a bit like a bad model issue. Had zero problems with that. Tool calls show clearly successful, agent interprets the type errors correctly, also understands when it's not due to that edit. What model are you using?
Lyapsus commentedon Jan 17, 2026
Don't have transcripts at hand but I'm pretty sure Gemini 3 Pro and Codex 5.2 both at max thinking levels showed such behavior.
And even if this is a matter of weak model - why not help it? This case is a free lunch to me in this regard
github-actions commentedon Mar 27, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
feat(lsp): 默认启用 LSP + 增量诊断 + VSCode Bridge LSP Backend + TUI 诊断渲染增强