Getting startedSet up integrationsCreate your first initiativeInvite your teamPlan today's workShare your first update
OverviewBuildingRunningReferenceTroubleshootingLocal AgentsSend to appUse in TerminalMonitoringHow agents runAgent SessionsBuild LocalBuild Cloud
DocsAPI Reference

Main

  • Home
  • About
  • Pricing
  • Vault
  • Changelog
  • Docs

Features

  • Roadmaps
  • Planning
  • Standups
  • Status updates
  • Insights
  • AI assistant / MCP
  • Integrations

Solutions

  • Startups
  • Dev shops / agencies
  • Software teams
  • Internal IT & platform teams

Alternatives

  • vs Jira
  • vs Linear
  • vs Asana
  • vs Monday.com
  • vs ClickUp
  • vs Notion

Company

  • Blog
  • Security
  • Log in
  • Sign up
  • Terms of Use
  • Privacy Policy

Resources

  • Docs
  • Community
  • API reference
  • CLI
  • Desktop app
  • SDK

© 2026 One Horizon. All rights reserved

FacebookInstagramThreadsXRedditTikTokYouTubeMedium


Workflows & Agents

A workflow is a reusable execution plan for agent work that needs more than one step. It can route work through agents, human review gates, shared branches, and workflow documents while keeping the run tied to the original initiative, bug, or todo.

Open Workflows from the main menu to check agents, definitions, recent sessions, and recent runs.

Workflow or direct agent assignment

Choose the smallest path that matches the work.

PathBest fit
Workflow runRepeatable work that needs planning, implementation, review, feedback loops, branch handoff, or durable workflow documents.
Local agentOne background agent session on your machine.
Send to appOne work item opened in a coding tool while a person stays in control.
TerminalCLI-driven handoff, local agent commands, or scripted task updates.
Cloud agentA shared service that stays online and claims queued sessions from your infrastructure.

Direct agent assignment and workflow runs use the same session and claim model. A workflow adds the saved execution plan: step order, route outcomes, human gates, runtime defaults, and artifact documents.

Core terms

TermMeaning
Workflow definitionThe reusable draft or published plan you edit in the workflow designer.
Workflow runOne launched copy of a published definition. Later definition edits apply to new runs only.
StepOne unit in the workflow, such as an agent step or human review step.
RouteThe configured outcome after a step, such as success, approve, feedback, or reject.
Agent sessionThe queued work an eligible agent claims and executes.
ClaimThe lease that lets one agent run one session. Work starts only after the claim succeeds.
Workflow artifactA structured plan, review, or result-summary document attached to the linked task.

Learning path

Start by choosing how agents run if you have not decided between workflows, local agents, apps, and custom agents.

Build a saved process in Building Workflows. That guide covers the designer, local agent setup from a workflow step, task modes, runtime defaults, routes, validation, and publishing.

Launch and follow active work in Running Workflows. That guide covers Send to..., lifecycle states, review handoffs, outputs, and active-run blocking.

Use Workflow Reference when you need technical details about execution, step types, task modes, branches, artifact documents, document blocks, or custom-agent responsibilities.

Fix known failures in Troubleshooting. Publishing, validation, launch, connectivity, execution, and handoff problems live there with the workflow FAQ.


PreviousSlack DiscussionsNextBuilding

Running

Launch workflows from work items, monitor active runs, review handoffs, and find outputs.

Reference

Reference workflow definitions, execution, step types, task modes, artifact documents, and agent responsibilities.

Building

Create workflow definitions, configure steps, route review outcomes, validate, and publish.

Troubleshooting

Fix workflow publishing, validation, launch, connectivity, execution, and handoff failures.

  • Workflow or direct agent assignment
  • Core terms
  • Learning path
  • Back to top