Skip to main content
Enable the standard toolbox — the shipped default tools and their wrapper and transformer extensions — from a manifest. The standard toolbox is a batteries-included default set of generic tools and tool extensions. Nothing loads automatically — you opt in per module by naming it in the manifest, exactly like your own code. The tools are self-contained utilities; the extensions are the live demonstration of the clip-on-powers model — memoize, batch, proxy, chain, and meter any tool.

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 — cache memoizes results, batch fans one tool over many inputs, chain pipes one tool’s output into another, output_schema forces a tool’s output to a JSON Schema, proxy routes its connections through a forward proxy, prometheus_metrics meters it.

Enable the modules

Load a tool module under tools[].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
With an extension loaded, attach it to a tool through that tool’s 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
The tools that take no arguments run bare:
The rest take their arguments by name — inspect any tool’s exact input schema with 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