examples/presets/minimal_preset.yaml
Create a preset
Name the base tool and the fixed kwargs to bake. The baked keys are removed from the exposed schema; the remaining arguments keep the base tool’s real typed schema. Create writes the durable store row and then registers the live tool.validate:
Save a new version
Save a new version when the configuration changes. Omitted fields carry forward from the active version;--clear-tags and --extensions '[]' send the explicit clear sentinel.
Roll back
Make a prior version active again. Rollback appends a new version pointing at the target body — it never rewrites history.Tag a version
Label an immutable version body without rebinding the tool. Passing no tags clears them to[].
Rename a preset
A preset’s name is its live tool name, so renaming it rebinds the tool — the new name binds before the old is torn down. First check whether other presets compose this one (their authored-agent specs name it as a tool); a rename blocks with a409 listing every referee until you update them:
The versioning spine is one mechanism, shared by many kinds. Presets, access-control policies, and authored agents all ride it — append-only versions, an active pointer, rollback, per-version tags, and rename over an opaque body.
validate, referees, set-version-tags, and rename:
examples/presets/presets_help.sh
See also
- Presets — what a preset is and how binding works.
- The versioning spine — the shared append-only version model.
- Author an agent — an authored agent is a preset over a spec-runnable agent.
- CLI reference — the full
tai presetssurface.

