Use a recipe for a task whose steps and site you can review in advance. Agents create drafts. A person approves the exact version in Recipes before it can run.

Create a draft

This example fills a form on your own test site. Replace the site origin and visible control label with real values from a fresh read. It does not submit the form.

{
  "name":"space",
  "arguments":{
    "action":"recipe_save",
    "name":"Fill name",
    "site":"https://example.com",
    "params":["customer"],
    "steps":[{
      "tool":"type",
      "locator":{"kind":"input","label":"Your name"},
      "args":{"text":"${customer}"}
    }]
  }
}

The public example.com page has no such form. Use this shape on a site you own that has the control. For an existing task, recipe_from_timeline can make a draft from recorded steps.

Review and run

Inspect the draft, its site, locators, parameters and expectations in Recipes. Approve only the version you reviewed. Then run:

{"name":"space","arguments":{"action":"recipe_run","name":"Fill name","params":{"customer":"Ada"}}}

List available recipes with space and {"action":"recipes"}. Changes and imports create drafts that need approval again. A failed expectation stops the run and identifies the failed step. Do not blindly replay a submit or payment action after an uncertain result.

Bound the work

A recipe has at most 50 steps and a five-minute run limit. Permission rules, site limits and the human-control lock still apply. Parameters are values, never instructions to execute. Use stable labels and expectations rather than a control number captured on an old page.