Script

Runs a piece of code the architect wrote for your workflow: calculations, data transformations, or logic that's better done exactly than approximately.

For deterministic work where judgment isn't wanted: math (tax, discounts, totals), data formatting, or calling several APIs in a strict order. The code is written and tested at setup; only its inputs vary between runs. Text drafting and decisions stay with the runner agent.

What the architect sets up

• The code itself, written and test-run at setup
• What it takes in and what it produces
• When it runs, and what a failure should mean for the run

How it behaves in a run

• Runs when the agent decides it's needed, or automatically when a stage begins or completes.

Related

• Stages & components: how components fit into a workflow
• Showcase: see components like this at work in real workflows

For developers: the API and MCP server identify this component as runnable_script.