[BUG] Only getDiagnostics is available for the IDE integration

[oliverdain]

Bug Description

I have a pretty-much standard install. For a while I could open claude and ask questions like "what does the current file do" but now it doesn't know what the current file is. I think the only tool available to it via the IDE integration is getDiagnostics

To Reproduce

Steps to reproduce the behavior:

1. Start Claude Code integration with <leader>cc (I use <leader>cc instead of <leader>ac)
2. Ask claude "what file is currently open" or "what is the file in the current buffer", etc.
3. It either says it doesn't know or it tries to run getDiagnostics which doesn't help

or

1. Start Claude code with <leader>cc
2. Run /ide and it says it's connected to neovm.
3. Ask claude, "What tools do you have available via the neovim ide integration?". It says:

● Based on what's available, I have the following IDE integration tools:                                                                                                                                                                    
                                                                                                                                                                                                                                            
  - mcp__ide__getDiagnostics - Get language diagnostics (errors, warnings) from the editor, optionally filtered by file URI.                                                                                                                

Expected Behavior

A more complete integration.

Environment

• Neovim version: 0.11.1
• Claude Code CLI version: 2.1.12
• OS: Linux (Debian Trixie)
• Plugin version: aa9a5ce is the commit hash

[oliverdain]

I also explicitly switched to version v0.3.0 of the plugin and that didn't change anything.

[oliverdain]

I did some debugging with Claude having it read the code in this plugin, in my lazy.nvim configuration, check the ~/.claude/ide lockfile, etc. and it says:

● That's revealing. The plugin does implement get_open_editors and get_current_selection as MCP tools. But on my end, the only tool I see from the IDE MCP server is getDiagnostics. I should have tools like:                              
                                                                                                                                                                                                                                            
  - mcp__ide__getOpenEditors                                                                                                                                                                                                                
  - mcp__ide__getCurrentSelection                                                                                                                                                                                                           
  - mcp__ide__openFile                                                                                                                                                                                                                      
  - mcp__ide__getWorkspaceFolders                                                                                                                                                                                                           
  - etc.                                                                                                                                                                                                                                    
                                                                                                                                                                                                                                            
  But I don't. Something is preventing those tools from being registered on my side, even though the WebSocket connection is established (the lock file exists and getDiagnostics works).                                                   
                                                                                                                                                                                                                                            
  This could be:                                                                                                                                                                                                                            
                                                                                                                                                                                                                                            
  1. A version mismatch — v0.3.0 is the latest release, but maybe Claude Code's client side has changed what tools it expects or how it registers them.                                                                                     
  2. A handshake/capability negotiation issue — the tools may be registered but Claude Code isn't exposing all of them to me.                                                                                                               
  3. A bug — either in the plugin or in Claude Code's MCP client for Neovim connections.                                                                                                                                                    
                                                                                                                                                                                                                                            
  I'd suggest filing an issue on https://github.com/coder/claudecode.nvim noting that only getDiagnostics is available while the other tools (getOpenEditors, getCurrentSelection, etc.) are not being exposed, despite the WebSocket       
  connection being active. Including the lock file content and your plugin version would help them debug it.                                                                                                                                

I'm not sure what to do with that, but hopefully it's helpful to you.