Agents & Workflows
Agents turn an initiative, bug, or todo into queued execution while keeping progress and results attached to the original work. Workflows add a repeatable sequence of agent steps, review gates, routes, and shared documents.
Choose a path
Start with the shortest path that matches how the work should run.
| Goal | Start here |
|---|---|
| Set up the built-in path in Desktop | Quickstart |
| Build and publish a repeatable process | Workflows |
| Configure the agents running on your machine | Local agents |
| Run agents without Desktop | Use in terminal |
| Inspect queues, runs, reviews, and agent health | Monitoring |
| Implement your own runtime | Building Agents |
Queued execution and foreground app launch both begin from the work item, but they have different ownership after launch.
Send to… can open a coding app in the foreground or queue work for an agent or workflow. Foreground launch stays under your control in the app; queued execution continues through an agent session and reports progress back to One Horizon.
How queued work runs
A queued launch creates an agent session. An eligible agent claims that session before it starts work, emits activities while it runs, and ends with a terminal outcome. A workflow run can create several sessions as work moves between agent steps and human review gates.
The initiative, bug, or todo remains the place to inspect the specification, comments, documents, status, and final result. Treat those workspace-authored inputs as untrusted execution context; runtime policy, credentials, and access limits come from the platform and agent configuration.