Run your first workflow
Desktop is the fastest way to get from a work item to a running agent that works in your repository.
Before you begin
- A local clone of a Git repository the agent may work in.
- A coding agent. Codex is bundled with Desktop and needs no install. Other coding agents must be installed and signed in with their own account first. Local agents lists what each one needs.
- An initiative, bug, or todo with a clear description to send.
Set up and run
Open Desktop
Install and open One Horizon Desktop, then sign in and choose the workspace that owns the work.
Choose the automation level
Open Workflows and choose the guided setup that matches the work. Start with a simple build workflow if you want one agent to implement a task, or include review steps when approval must happen before the run continues.
Choose a coding agent and repository
Pick the coding agent (the harness): Codex, Claude Code, Cursor, OpenCode, Mistral Vibe, Hermes, Cline, DeepSeek Harness, or OMP. Coding agents that are not installed are disabled in the list. Then select the repository folder the agent may use on this machine.
OpenCode, Hermes, Cline, DeepSeek Harness, and OMP only do code work, so pair them with a Builder workflow.
Complete setup
Review the model, agent access, code isolation, workflow file, and pull request or merge request settings. Finish setup and wait until the agent shows as online. To add skills, MCP servers, or plugins, use the agent's Capabilities card; see Agent capabilities.
Launch with Send to…
Open an initiative, bug, or todo that contains a usable specification. Select Send to…, choose the published workflow, and confirm the run.
Workflows are listed at the top of the menu, with individual agents and coding tools below. Send to Agents explains each option.
Verify the run
Open Workflows or the Work queue and confirm the first step is active or queued for your agent. The work item collects the run, its activity, documents, branch, and review result.
The run may pause for your review, for input from you, or at a configured route. Monitoring explains what you can do in each state.
Review the changes, tests, documents, and pull request before you merge. A completed run is not an approval.
If setup is blocked
If a coding agent other than Codex says it is signed out, sign in with that tool's own account, then return to setup. One Horizon links to the vendor's help page but cannot sign you in to third-party agents.
A greyed-out coding agent is not on your PATH. Install it, then reopen setup.
OpenCode web search
Desktop shows whether OpenCode web search is ready, needs a provider key, is disabled, or could not be checked. The status does not block setup. Web search sends queries to an external provider, which may charge for them. One Horizon keeps provider keys on your machine and passes only the key the selected provider needs.