Runs
A run is one execution of a teammate or task. Use runs for direct messages, follow-ups, and real-time output.
Create a run
Streaming (default and recommended)
Use the context manager so the stream closes cleanly even if you exit early.
Direct iteration is still supported:
Stream text only
Non-streaming
Follow up on a run
Follow-up messages create a new run that keeps context from the previous one.
runs.reply() is always non-interactive. It does not enable AskUserQuestion, approval mode, or plan mode.
Run options
When email_inbox=true, the response includes email_address — forward emails to that address to trigger future runs.
Set task_setup_tools=False when you want a public API run to stay limited to the teammate's normal tools. Set feedback=False when you want to disable the internal issue-reporting feedback tool. Replies inherit both settings unless you override them.
For permission and approval flows, see Human-in-the-Loop.
Run statuses
Run files
Runs can generate files. List and download them after execution.
What's next
- Teammates for trigger setup and teammate configuration
- Tasks for reusable work definitions
- Streaming & Events for full event taxonomy
- Webhook Events for outbound run notifications
