Skip to content

Conversation

@tcdent
Copy link
Owner

@tcdent tcdent commented Dec 21, 2025

  • Add Diagnostic struct and DiagnosticSeverity enum to ide module
  • Add IdeEvent::Diagnostics variant for receiving LSP diagnostics
  • Create diagnostics_tracking.lua that hooks into DiagnosticChanged
  • Update NvimHandler to parse codey_diagnostics notifications
  • Store diagnostics in App keyed by file path

Diagnostics are sent from Neovim after LSP updates (debounced 100ms),
providing the agent with error/warning information for edited files.

- Add Diagnostic struct and DiagnosticSeverity enum to ide module
- Add IdeEvent::Diagnostics variant for receiving LSP diagnostics
- Create diagnostics_tracking.lua that hooks into DiagnosticChanged
- Update NvimHandler to parse codey_diagnostics notifications
- Store diagnostics in App keyed by file path

Diagnostics are sent from Neovim after LSP updates (debounced 100ms),
providing the agent with error/warning information for edited files.
- Add get_diagnostics.lua that uses vim.wait() for DiagnosticChanged
- Add Ide::reload_and_get_diagnostics() for synchronous diagnostic fetch
- Modify tool completion handler to append diagnostics to results

After edit_file executes, the tool result now includes any LSP errors
or warnings, giving the agent immediate feedback on code issues:

  Successfully applied 1 edit(s) to src/foo.rs

  LSP Diagnostics:
    line 12: [rust-analyzer] error: cannot find value `foo`
    line 15: [rust-analyzer] warning: unused variable `x`

Uses event-driven waiting (DiagnosticChanged autocmd + vim.wait)
rather than polling, with a 500ms timeout.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants