Workflows
Build repeatable, reviewable work across coding agents.
A workflow turns recurring engineering work into a run you can inspect and repeat. Combine coding agents, scripts, typed outputs, pull requests, and Slack notifications; then launch the workflow yourself, from a chat, on a schedule, or from a poll feed.
Each agent keeps one session for the run and works through its ordered steps. Named inputs make the same definition useful across repositories, issues, and environments. Run it on your Mac or in the cloud, then inspect the sessions, outputs, file changes, and pull request before you merge.
Workflow definitions are personal in this beta. They can run against team repositories under your organization's policies, integrations, and budgets, but teammates cannot share or co-edit the definition yet.
Workflow tool access is explicit: a run does not inherit the plugins enabled in the chat or workspace it starts from. Grant Issues or Slack to the workflow in the editor. Those grants apply to the run as a whole today; the per-agent selection shown in the editor is not an enforcement boundary.
Building and running one
Build your first workflow
Create a daily standup digest and run it end to end.
The workflow editor
Arrange agents, steps, inputs, and integration grants.
Running a workflow
Launch from Workflows or chat, follow progress, and stop a run.
Parallel agents
Run independent agents together in isolated cloud lanes.
Triggers
Attach a trigger when the work should start without a manual launch:
Scheduling a workflow
Choose a recurrence, location, overlap policy, and missed-run behavior.
Polling triggers
Start one run for each new item returned by a feed you control.