Skip to content

Tools and add-ons ​

What the agent gets ​

ToolAnswers
contracts_searcha route: its controller, middleware and every file that calls it
graph_explainone symbol and all its connections
graph_affectedwhat depends on a symbol, across repositories
graph_routesseveral ways from A to B, with the routes on the way
review_contexta diff: what changed, what depends on it, the routes and screens it reaches, the docs to check
searchdocs and code by meaning
code_grepexact text with a regular expression: config keys, SQL, error messages
repo_mapa first look at a project: what most of the code leans on; with unused, dead-code candidates

Long answers come in pages with a cursor; connections and problems show the service map and its gaps.

Add-ons ​

Off until you install them; an add-on that is off adds no tool, page or route.

Add-onkb addon install … givesNeeds
tool-multicallbatch: several tool calls in one request—
code-moderun_code: a small program that calls the tools, in a sandboxNode 22+
fast-routesgraph_routes on a Rust core, 2-3x fastergraphify via uv or pipx
metricsGET /metrics for Prometheus, Grafana or PMM—
admin/admin: status, charts, usage, sign-in clientson a shared server: KB_ADMINS
auditan Audit tab: sign-ins, admin actions, every tool call with user and argumentadmin

kb addon list shows what is on, kb addon remove <name> switches one off. An add-on can also live outside this repository, under its own licence: kb addon install <folder with plugin.py> (see bin/plugins.py for the four names a plugin defines). A team server with browser sign-in and access per project: the shared server; it asks your own system who may see what through two webhooks, access protocol.

AGPL-3.0-or-later