
The local-first workbench for orchestrating coding agents.

AI made coding faster.
Helmor is about finishing the rest of the loop — orchestrating, reviewing, testing, merging, and actually shipping software.
Helmor runs many coding agents in parallel, each in its own isolated git
workspace — conversation, diffs, editor, terminals, and one-click PR actions
in one window. Everything lives locally under ~/helmor/.
helmor CLI and MCP server; your terminal or another agent can drive Helmor./ in the composer.More on the way — Slack & GitHub context, plan mode, and agent-driven orchestration.
flowchart LR
A[Add a repository] --> B[Create a workspace]
B --> C[Prompt an agent]
C --> D[Review and ship]
D -.->|repeat in parallel| B
~/helmor/workspaces/.macOS (Apple Silicon & Intel) · Windows (x64)
On first launch, connect GitHub or GitLab and sign in to your first agent. Agent CLIs are bundled — nothing else to install.
Install from Settings → Experimental → Command Line Tool. Works against the same local database as the app — even while it is running.
helmor repo add /path/to/repo
helmor workspace new --repo myapp
helmor workspace list
helmor send --workspace myapp/feature-x "Add a test for the parser edge case."
helmor workspace status myapp/feature-x
helmor workspace run-action myapp/feature-x # create PR, merge, fix CI, …
helmor mcp # MCP server over stdio
Workspaces use repo-name/directory-name shorthand. Every command supports
--json. Run helmor --help for the full reference.
Example — an agent ships a fix:
helmor workspace new --repo myapp --name fix-auth
helmor send --workspace myapp/fix-auth "Add tests for the token refresh path."
helmor workspace status myapp/fix-auth
helmor workspace run-action myapp/fix-auth
Architecture, commands, and test layout live in AGENTS.md.
To get started locally: bun install && bun run dev.
Or —
Open Helmor, Import Helmor, Ask Helmor:
"How do I contribute to Helmor?"
That's the guide.
$ claude mcp add helmor \
-- python -m otcore.mcp_server <graph>