Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.224 ·

Second LSP tool schema, one strict shape per operation

The language-server tool gained a per-operation schema, but nothing chooses it over the old one.

Under the hood Nothing to try yet In Development
JSON All of v2.1.224
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
LSP ToolsArea: what it touches
In DevelopmentKind: in v2.1.224,
In DevelopmentSection of the release

A strict per-operation LSP schema exists alongside the flat one with no selector between them.

What

A new schema for the language-server tool splits it into a separate strict object per operation (goToDefinition, findReferences, hover, documentSymbol, workspaceSymbol, goToImplementation, prepareCallHierarchy, incomingCalls, outgoingCalls), each with its own field descriptions, so arguments are validated per operation instead of against one flat shape. The old flat schema is still in the build and nothing in this group decides which one the tool presents.

Details
  • The workspaceSymbol variant drops the "(workspaceSymbol only)" qualifier from its query description, since the field now exists only there.
Evidence

The symbol name or partial name to search for. Most language servers return no results for an empty query.

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.224 →

Feedback