Back to the blog
Articleverboo codetutorialtroubleshootingdev tools

/doctor in Verboo Code: how to read your install diagnostic

MafraNovember 19, 20265 min read

The symptom is always the same: the command works, but something is off. A session that cannot find a file, an update that never arrives, a permission warning you have been ignoring for weeks. Before reinstalling, there is one command that dumps the state of your installation on a single screen.

It is called /doctor. It runs inside the Verboo Code session and changes nothing: it reads and reports.

What does /doctor do?

It checks how Verboo Code was installed and reports what it finds: installation type, version, path, the binary your shell invoked, the config install method, the status of file search, the update channel, write permissions on the global directory and sandbox dependencies. It also collects the context warnings that usually go unnoticed, such as an oversized CLAUDE.md, inflated agent descriptions and MCP servers that burn tokens before you type anything.

It is a session command, implemented as local-jsx. There is no equivalent shell subcommand: you open verboo and type it there.

How do you run /doctor?

Open Verboo Code in any directory and type the command. Reading happens immediately and the panel stays on screen until you close it.

$ verboo

> /doctor

Diagnostics
└ Currently running: npm-global (0.15.43)
└ Path: /usr/local/lib/node_modules/@verboo/code
└ Invoked: /usr/local/bin/node
└ Config install method: npm-global
└ Search: OK (bundled)

Updates
└ Auto-updates: Yes
└ Update permissions: No (requires sudo)
└ Auto-update channel: latest
└ Latest version: 0.15.43

The values above are sample output. What matters is reading the first five fields of the Diagnostics block in order, because they answer the most common question: when a problem shows up, is the installation you think is running actually the one running?

What does each block mean?

BlockWhat it showsWhen it matters
DiagnosticsInstallation type, version, path, invoked binary and config methodWhen behavior does not match the version you think you have
SearchWhether file search works and where the binary comes fromWhen the session cannot find project files
UpdatesWhether auto-update is on, whether it has permission, and which channelWhen a new version exists and never arrives
SandboxWhether sandbox dependencies are presentWhen commands fail oddly inside the sandbox
Context Usage WarningsMemory files and MCP servers that consume contextWhen the session feels smaller than it should
Invalid SettingsConfig keys that failed validationWhen an option you set simply has no effect

How do you fix the most common warnings?

Each warning points to a specific fix, and most of them are one line.

Warning: Multiple installations found

There are two copies of Verboo Code on the machine and your shell may be calling the one you never update. The block lists the type and path of each. Compare that with what the shell resolves:

which -a verboo
npm ls -g --depth=0 2>/dev/null | grep -i verboo

The second list shows the global npm copy. If the two point to different paths, uninstall the one you do not use. Keeping both is the most common source of the "I updated and nothing changed" symptom.

Update permissions: No (requires sudo)

The global directory belongs to root and auto-update cannot write to it. Either install with an npm prefix owned by your user, or update manually with sudo. The panel does not fix this on its own, it only reports it.

Search: Not working

File search is not operating. The value in parentheses tells you where the binary was supposed to come from: bundled when it ships inside the package, vendor when it comes from the distribution, or the path of a system binary. When the mode is system and that path no longer exists, reinstall the package.

Context Usage Warnings

Three limits show up here: a memory file that is too large per file, agent descriptions adding up to too many tokens, and MCP tools above the context ceiling. The list of top contributors comes sorted. Cut what you do not use instead of raising the limit.

Unreachable Permission Rules

One of your permission rules will never be evaluated because an earlier rule already decides the case. This is the kind of config that looks active and is not.

Invalid Settings

Some key in the settings file failed validation. The panel shows the key name and the reason, which saves you from hunting through a large JSON file.

Does /doctor show MCP server problems?

No, and that is intentional, but it confuses people. /doctor runs before MCP connections are established, so the MCP tool count can come back empty even with servers configured. The context warning about MCP only appears once tools are loaded.

For MCP server diagnostics the path is /mcp, which lists each connected server with its status. Use /doctor for the environment and /mcp for the server.

When /doctor does not solve it?

It describes state, it does not repair anything. If the panel is clean and the problem persists, the next step is looking at the session rather than the installation: whether the model answered what you expected, whether the project config file was read, whether the working directory is the one you think. In those cases the answer is usually in the session history, not in the machine diagnostic.

/doctor exists so you stop reinstalling on a hunch. Run it before touching anything, read the Diagnostics block from top to bottom and fix the first warning that appears. If you are not on Verboo Code yet, installation and the first command are at verboo.ai.

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

Related articles