Skip to main content
Pick the smallest primitive that matches the work. This keeps project structure clear and prevents overlapping agents, workflows, runs, and integrations.

Quick choice

Decision rules

Common pairings

Verify it worked

Before building, write down the primitive and why it owns the work. Then check the matching guide:
  • If the guide’s first example solves your shape, continue there.
  • If you need two or more primitives, start with the one that owns the triggering event.
  • When choosing between Task and Run, remember that a task defines the work and a run executes it durably.
Run the guide’s example or validation command before adding another primitive.