Helmor CLI
A desktop app that runs Claude Code, Codex, Cursor and OpenCode in parallel, each in its own git worktree, with a CLI and MCP server for control
- 1,308 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- Agents work inside your repositories and can create PRs, merge them and fix CI with one button
- The mobile companion opens control of the desktop through a Cloudflare tunnel
- The CLI and MCP server let another agent manage workspaces and send prompts
Install
- Works in
Manual install
helmor mcpStarts the MCP server over stdio. First install the helmor command under Settings, Experimental, Command Line Tool.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Agents work inside your repositories and can create PRs, merge them and fix CI with one button
- The mobile companion opens control of the desktop through a Cloudflare tunnel
- The CLI and MCP server let another agent manage workspaces and send prompts
This is third-party code. Review the repository files before installing.
What it does
Helmor runs several coding agents in parallel: each task gets its own git worktree and branch, and the conversation, diffs, editor and terminals sit in one window. It connects Claude Code, Codex, Cursor, OpenCode and Kimi Code with your own logins, keys and custom providers, and the agent CLIs are bundled with the app. From the window you can create a PR or MR on GitHub and GitLab, merge, fix CI, resolve conflicts and build a stack of dependent PRs. For automation there is the helmor command and the helmor mcp server, both working against the same local database as the app. The helmor-cli skill teaches an agent those commands and the stack, break and restack flows. Data stays local under ~/helmor/.
Who it is for. For developers who run several agents against one repository and want to read diffs, run tests and ship PRs from one window.
Good fit when
- Several tasks in one repository must run in parallel with agents that must not step on each other
- A large change should become a stack of dependent PRs with /helmor-cli stack, break and restack
- You want to read diffs, edit code in an editor and open a terminal next to the agent conversation
- Workspaces must be driven from scripts, or another agent should send prompts with helmor send
- Prompts should run in the agent's native TUI, which Terminal Mode provides
Not a fit when
- You want a single agent in the terminal with no separate app: Helmor is a window with workspaces
- You work on Linux: the README names only macOS and Windows
- You need an MCP package to launch through npx or uvx: the MCP server ships inside the app as helmor mcp
- The repository lives outside GitHub and GitLab: PR and MR actions are described for those two
Example request
Create a workspace in the myapp repository named fix-auth, send the agent a task to add tests for the token refresh path and show the statusLimitations
This is an app, not a package: you install it from a GitHub release. The README names macOS (Apple Silicon and Intel) and Windows (x64). The helmor command is installed from the app settings (Settings, Experimental, Command Line Tool). The mobile companion over a Cloudflare tunnel is marked experimental. You must sign in to at least one agent, so access without a VPN depends on the agent and its provider you choose.
How to disable. Quit the app and uninstall it like any program. Workspaces and the database live under ~/helmor/ and can be removed separately. Helmor skills are removed from your agent's skills directory.
FAQ
Which agents work in Helmor?
Claude Code, Codex, Cursor, OpenCode and Kimi Code. You sign in with your own logins or keys, and custom providers can be added. The agent CLIs are bundled, so you do not install them separately.
How do I control Helmor from the terminal or from another agent?
Install the helmor command under Settings, Experimental, Command Line Tool. It works against the same local database as the app, even while the app is running. helmor mcp starts an MCP server over stdio, and every command supports --json.
How do I install Helmor skills?
Install them during onboarding or under Settings, Helmor Components. In the composer, skills open with the / key. The helmor-cli skill accepts stack, break and restack for working with PR stacks.
Where does Helmor keep its data?
Locally under ~/helmor/. For each task it creates a fresh git worktree and branch under ~/helmor/workspaces/.
Which systems does Helmor run on?
The README names macOS (Apple Silicon and Intel) and Windows (x64). The app downloads from the GitHub releases page, and the agent CLIs are bundled.
Discussion
No questions or reviews yet.
Related
CLI toolsA CLI that lets agents in different terminals message, watch and spawn each other
A tmux-based TUI that runs Claude Code, Codex and other agents in one list: status, quick prompts, worktrees and diff review
A terminal app for running several Claude Code, Codex, Gemini CLI and Aider sessions in parallel, each in its own tmux session and git worktree
One runtime for Claude Code, Codex, OpenCode and more: a run counts as done only when checks the agent did not write pass
A memory and coordination layer for coding agents: specs and issues live in git while agents work in parallel
A Rust app for macOS, Linux and Windows: skills, MCP servers, plugins, hooks and configs of 17 AI agents in one window, with a security audit
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Helmor (this entry) | no | 1,308 | ||
| CLI Agent Orchestrator | no | 1,485 | a CLI where a supervisor hands tasks to agents in terminal sessions, with no desktop window of diffs | |
| Ralph Orchestrator | no | not required | 3,190 | a CLI that loops an agent until the task is done instead of keeping parallel workspaces |
README in short
The README opens with the idea of finishing the loop after the agents write code: orchestrating, reviewing, testing and merging. It then lists the features (isolated workspaces, bring your own agents, review without leaving the window, one-button PRs, Terminal Mode, a quick panel on Shift-Option-Space, CLI and MCP, skills, an experimental mobile companion), a four-step flow from adding a repository to merging, the releases link and the helmor commands with an example of an agent shipping a fix.