baron_recipe_run
Execute a named recipe as one deterministic workflow. Supply required inputs to run start-to-finish, or resume a failed run with its runId to continue without repeating completed steps.
Instructions
Run a named recipe end-to-end as ONE deterministic, rule-enforced workflow (the engine — not you — enforces the step order). Supply all required inputs (from baron_recipe_list) in inputs; a missing required input errors rather than prompting. Prefer this over composing the individual issue/scm/ci tools yourself for a packaged workflow. Returns the run context as JSON (with its runId), and — when the recipe had anything to say — a SECOND text block with its messages. Read that block: it is where a recipe reports what it could not verify (task-land warns there when it merged past checks it could not see). Every run is journaled: if one fails partway, do NOT run it again from scratch (that repeats the steps that already mutated the provider — a second PR). Call this with resume: <runId> from the error instead: completed steps are replayed from the journal and the run carries on from where it stopped.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "baron_recipe_run"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Recipe name (e.g. task-start). Required unless `resume` is given. | |
| inputs | No | Values for the recipe's `ask` inputs, keyed by input name. | |
| resume | No | The `runId` of a run that stopped (from its error, under details.run.id): continue it instead of starting a new one. Its inputs and answers are restored from the journal. |