Where your agents work, whoever made them.
Run coding agents in Teams. Set the rules with Flows, follow each Run, and step in where the work needs you.
Two agents, one brief, a browser each. The judge picks; you merge.
Works with the agents you already run
…or any agent that speaks ACP. What each one can do →
Write, check, review, fix, land: every Run follows the Flow you set. When a check fails or a reviewer asks for a change, you watch it loop back, and you see the one step waiting on you.
Skip the tour of agent terminals. See what is working, what is in review and what is blocked on you, with the checks, the diff and the pull request on each card.
Which agent spent what · Before a limit stops you · Where the work went. Docs →
Every Team, one board |
Follow each step |
Set the process once |
See what each skill costs |
Every runtime, ready or not |
Ask first, pick a folder later |
Script it, or let your agent run it. Docs →
- No new bill. Each agent keeps its own sign-in, so the plans you already pay for keep working. HarnessDesk is free and adds nothing on top.
- Your code stays with you. Agents work in your own folders, and the desk keeps its records on your machine. Data boundaries →
- Read it before you trust it. HarnessDesk is open source under the MIT license. Read the source on GitHub.
Also in the box:
- Hand-off: pass a conversation to another agent with a packet it can pick up.
- A browser per Seat: each agent opens, clicks and reads its own pages.
- Agents: reusable briefs and ceilings, with ten built-in roles to start from.
- Plugins. Thirteen built in. HarnessDesk projects its 90 built-in plugin tools into each agent’s tool interface. Docs →
- One policy, one audit log: the same rules, whichever agent asked.
Settings › Account opens sign-in in your system browser. Approve the named desk and matching code there; return to manage its name, sign out, or delete the account. Agent sign-ins and local work remain separate. The host's requests and stored data are listed in data boundaries.
With local phone access enabled, Settings › Phone shows a code to scan on the same network. Allow the phone on the desk; pairing needs no account link. Settings › Permissions controls Git write steering and its project overrides; the Git record shows gateway writes and observed outside heads.
Lead is an optional conversation for planning work, approving its allowances
and following workers, checks and reviews. It needs the startup opt-in
HARNESSDESK_LEAD=1 and a runtime whose permission model blocks the network for
its child: a standalone host on Node 26, or the desktop app, which carries one.
Where no runtime passes, Lead shows as unavailable with the reason; ordinary
sessions remain usable. See the interface.
Download the signed, notarized app for macOS 13+, Apple silicon or Intel, from the latest release. It updates itself. Then bring an agent you already use: getting started covers installing and signing in to the main ones, and how to add any other agent from the ACP registry or by its own command.
Build from source with Node 22.19+ and pnpm 10:
pnpm install
pnpm build
pnpm appCONTRIBUTING.md is the way in; security reports go to SECURITY.md.
MIT. HarnessDesk is an independent project, not affiliated with, endorsed by, or sponsored by any of the vendors whose agents it drives; their names appear here only to identify their software. The extension kernel is DeepSeek's Cordis (MIT), and the Codex protocol types are generated from openai/codex (Apache-2.0). See THIRD_PARTY_NOTICES.md and TRADEMARKS.md.