When to reach for it
- A tool from the toolbox gives you a ready-made capability — the current time as a structured object, a random UUID, an HTTP request, embedding vectors.
- An extension from the toolbox clips a power onto an existing tool without changing it —
cachememoizes results,batchfans one tool over many inputs,chainpipes one tool’s output into another,output_schemaforces a tool’s output to a JSON Schema,proxyroutes its connections through a forward proxy,prometheus_metricsmeters it.
Enable the modules
Load a tool module undertools[].module and an extension module under extensions_modules. Import paths are the module names; the base install stays light, and each heavier module is gated behind an optional dependency that fails loudly at import if missing.
manifest.yml
extensions map or tai tools apply — see Apply an extension.
Run a tool with --kw
Run any registered tool synchronously with tai tools run <name>. Pass its arguments as repeatable --kw key=value pairs — each value is parsed as JSON, falling back to the literal string — or as one JSON object with --kwargs:
examples/toolbox/run_tool_kw.sh
tai tools schema <name>:
The standard set
The tools and extensions the toolbox ships. This table is generated from the ecosystem catalog, so it never drifts from the package.Confirm what loaded
The full, always-current list of toolbox tools and extensions — names, kinds, and the optional dependency each needs — lives in the ecosystem catalog. Per-tool specifics (formats, session behavior, the extras to install) live in the toolbox package’s README, linked from the catalog.
See also
- Tools and extensions — the model the toolbox demonstrates.
- Apply an extension — attach a toolbox extension to a tool.
- Ecosystem catalog — the full toolbox catalog and its repository.
- CLI reference — inspect what loaded.

