[BUG] IDE integration with external Claude Code missing most tools

[CallumHoward]

Bug Description

Not 100% sure if this is a bug or working as intended (not implemented).

I have claudecode.nvim set up and working with

• getDiagnostics (Claude to IDE)
• selection_changed (IDE to Claude)

but none of the others from PROTOCOL.md, eg:

• openFile
• openDiff
• getOpenEditors

To Reproduce

My config (LazyVim):

  {
    "coder/claudecode.nvim",
    enabled = true,
    opts = {
      terminal = {
        provider = "none",
      },
      auto_start = true,
    },
    config = true,
  },

Steps to reproduce the behavior:

1. Open nvim with files
2. claude --ide in the same cwd
3. Prompt: "What files are open in my ide?"

Expected Behavior

A clear and concise description of what you expected to happen.

Environment

• Neovim version: 0.12.0
• Claude Code CLI version: 2.1.84
• OS: Tahoe 26.4
• Plugin version: main commit 432121f

Error Messages

If applicable, add error messages or logs.

Paste any error messages here

Additional Context

From Claude

  All tools are registered on the Neovim side (verified via
  claudecode.tools.init.lua:register_all). The WebSocket server
  exposes them. Claude Code CLI appears to only surface
  getDiagnostics as a model-callable MCP tool — the rest are
  used internally by the CLI runtime.

  Question: is this by design? If so, could openFile and
  getOpenEditors also be exposed as model-callable tools?

[CallumHoward]

Well, apparently it can use openDiff. Maybe it is working as expected then?

[mintplo]

It seems that Claude code don't call openDiff in bypass mode or auto mode.

When I set debug level, AI reviewed the debug logs. there are not openDiff call.