Back to the blog
Articletutorialverboo codedev toolsagente de programação

LSP in Verboo Code: how the agent finds definitions and type errors

MafraNovember 20, 20266 min read

The agent edits a TypeScript file, runs the command you asked for and says it is done. The type error shows up later, when you build or CI complains. Until then it worked in the dark: read the file, inferred what it could and moved on.

The /lsp command in Verboo Code closes that gap. It connects a language server to the agent, and from then on the conversation queries definitions, references, types and diagnostics for real instead of guessing from the file text.

The path has four steps and all of them happen in the terminal: check the current state, find the plugin for your project, install the binary and the plugin, and confirm the agent can now see the code.

What changes when the agent has a language server?

It gains two things that do not exist without LSP: structured queries against the code and automatic diagnostics.

The queries come from a tool that answers nine operations. Each one requires a file path, a line and a character, counted from 1, the same way your editor does:

OperationWhat it returns
goToDefinitionWhere the symbol is defined
findReferencesEvery use of the symbol in the project
hoverType and documentation at that position
documentSymbolFunctions, classes and variables in the file
workspaceSymbolSymbols across the whole workspace
goToImplementationImplementations of an interface or abstract method
prepareCallHierarchyStarting point for the call hierarchy
incomingCallsFunctions that call the function at that position
outgoingCallsFunctions it calls

Diagnostics are the other half. When the server publishes an error after an edit, Verboo Code delivers that diagnostic into the conversation as an attachment, without you asking. Delivery is capped at 10 diagnostics per file and 30 per batch, and anything already delivered does not come back on the next turn.

How do you check whether an LSP server is already active?

Run /lsp status inside the session. It shows the initialization state and every server that came from a plugin.

> /lsp status

LSP status
Initialization: success
Configured plugin LSP servers: 1
- typescript (state: running)
  command: typescript-language-server --stdio
  extensions: .cjs, .cts, .js, .jsx, .mjs, .mts, .ts, .tsx

If the list is empty, the output ends with Configured plugin LSP servers: none. A server in stopped is not a failure: it is a lazy start that comes up on the first query and saves memory in projects that do not use that language.

How do you find the right plugin for your project?

Run /lsp recommend pointing at the folder, a file or an extension. The command reads the project extensions, ranks the most common ones and matches them against the LSP plugins in the installed marketplaces.

> /lsp recommend .

LSP recommendations for .
- typescript-lsp@claude-plugins-official (not installed, binary: found)
  command: typescript-language-server
  extensions: .cjs, .cts, .js, .jsx, .mjs, .mts, .ts, .tsx
  description: TypeScript/JavaScript language server for enhanced code intelligence
  next: /lsp install typescript-lsp@claude-plugins-official

Read the two marks inside the parentheses as separate questions. not installed is about the plugin. binary: found is about the server executable, which must be on PATH. When the binary is missing, the output replaces the last line with a block containing the install command and the verification command.

Verboo Code has its own marketplace, verboo-plugins, and keeps the ecosystem's official plugin marketplace as a secondary source. Language plugins live in the second one, and /lsp recommend registers it on its own when it finds no candidate. That requires git to be available. Without it, the output warns that the marketplace is unreachable.

How do you install the binary and the plugin?

Two pieces, and order matters: first the server executable, then the plugin that teaches Verboo Code how to call it. The commands in the table are the ones /lsp recommend prints when the binary is missing.

LanguagePluginInstall the binaryVerify
TypeScript and JavaScripttypescript-lspnpm install -g typescript typescript-language-servertypescript-language-server --version
Pythonpyright-lspnpm install -g pyrightpyright-langserver --help
Gogopls-lspgo install golang.org/x/tools/gopls@latestgopls version
Rustrust-analyzer-lsprustup component add rust-analyzerrust-analyzer --version
C and C++clangd-lspsudo apt install clangdclangd --version
PHPphp-lspnpm install -g intelephenseintelephense --version
Rubyruby-lspgem install ruby-lspruby-lsp --version
C#csharp-lspdotnet tool install --global csharp-lscsharp-ls --version

With the binary on PATH, install the plugin by its full id, with the marketplace after the @:

> /lsp install typescript-lsp@claude-plugins-official

Installed typescript-lsp@claude-plugins-official. Activated 1 plugin LSP server.

The install is user scoped: it applies to every project on the machine, not only the open folder. To undo it, run /lsp uninstall typescript-lsp@claude-plugins-official.

The binary must be on the PATH of the process that opened Verboo Code. If you install Node with nvm, this is where it usually breaks: the npm global directory only joins PATH when nvm is loaded. Open the terminal, load nvm and only then call verboo. If /lsp recommend says binary: missing after an install that looked correct, run which typescript-language-server before blaming the plugin.

How do you know the agent can now see the code?

Run /lsp status again and confirm the server is listed. Then ask for a query only the server can answer, such as where a type is defined or who calls a function. The agent uses the LSP tool with line and character and returns the real position, not the result of a text search.

The fastest test is an error. Ask for an edit that breaks a type on purpose. With the server running, the error comes back in the same response, before any tsc. Without a server, the tool answers No LSP server available for file type: .ts and the agent only finds out when it runs the build.

What if the server does not start?

Three causes cover almost everything: binary off PATH, missing plugin and stale configuration held in memory.

  • binary: missing in the recommendation: install the executable and confirm with the verification command from the table.
  • Configured plugin LSP servers: none: the plugin is not installed or is disabled. /lsp install handles the first case.
  • Server with an old configuration: /lsp restart restarts the manager and reloads the plugins.
> /lsp restart

LSP restarted. 1 server configured.

When initialization fails, /lsp status shows Initialization: failed with the error message, and each failing server carries a last error line. That is where the real cause appears, such as a command that does not exist or a startup timeout.

If the failure is environmental rather than server side, /doctor closes the diagnosis: it reads installation, PATH and configuration before you reinstall anything.

/lsp does not guess your stack: it reads the project, prints the plugin and the binary install command. If your project is TypeScript, open the folder in Verboo Code and run /lsp recommend . to see the real recommendation for your repository.

Enjoyed this article?
Share knowledge with your network.
// Read also

Related articles