Skip to main content
Once an agent exists and is configured, the CLI is the fast path for triggering it, watching it, and inspecting what happened.

​
Run it

Agents run asynchronously by default — agent run schedules and immediately returns a run id. That’s the opposite default from workflow run, which is synchronous by default. Pass --sync to wait, or --watch to poll until the run reaches a terminal state.

​
Check what’s been running

execution get works on any run id — one you just started, one from a scheduled cadence, or one started from Studio. It’s the single place to answer “what happened on run X,” regardless of what triggered it.

​
When a run needs a human

Some workflows deliberately stop and wait for a person before doing something risky or public (publishing content, a bulk data change). That’s the approvals gate:
This isn’t specific to agents — any workflow can file an approval request — but it’s the mechanism you’ll hit if an agent’s workflow is wired to gate its output. See approvals for the full flow and how to gate your own workflow.