Helmor Local Agent Workbench
Run coding agents in parallel in isolated Git workspaces, then review, test, and ship their work.
What does this agent do, and when should you use it?
Helmor is a local-first workbench for multi-agent software development, with data and workspaces kept under `~/helmor/`. It creates a separate Git worktree and branch for each task so coding agents can work in parallel without sharing a workspace. The application brings conversations, diffs, a Monaco editor, terminals, and PR actions into one window, with GitHub and GitLab flows for creating and merging PRs or MRs, fixing CI, and resolving conflicts. It supports bringing your own Claude Code, Codex, Cursor, OpenCode, or Kimi Code credentials, API keys, and custom providers. Helmor also exposes a `helmor` CLI and an MCP server over stdio; an experimental mobile companion uses a Cloudflare tunnel to start tasks from a phone browser.
A user adds a local repository through the app or with helmor repo add /path/to/repo, then creates an isolated task branch and worktree using helmor workspace new --repo myapp. Tasks are sent to a signed-in coding agent through the interface or helmor send --workspace myapp/feature-x "...", while Helmor presents the agent conversation, code changes, editor, and terminal for that workspace. helmor workspace status checks workspace state, and helmor workspace run-action runs available delivery actions such as creating a PR, merging, or fixing CI. helmor mcp starts an MCP server over stdio, and every CLI command supports --json.
- A developer handling several bug fixes or features who wants a separate Git worktree and coding-agent task for each branch.
- An engineer using Claude Code or Codex who wants to inspect generated diffs, edit code in Monaco, and use a terminal beside the conversation.
- A maintainer working through GitHub or GitLab delivery who needs to create or merge PRs/MRs, address CI failures, and resolve conflicts from a workspace.
- A command-line-oriented developer who wants to automate local task workspaces with `helmor workspace new`, `helmor send`, and `helmor workspace status`.
- A developer who wants a terminal or another agent to drive the local workbench through Helmor’s stdio MCP server.
What are this agent's strengths and limitations?
- Each task receives its own Git worktree and branch, which is designed to prevent parallel agents from working over one another.
- Conversation, diffs, Monaco editing, terminals, and PR/MR actions are co-located, supporting review and shipping in one workbench.
- It explicitly supports Claude Code, Codex, Cursor, OpenCode, and Kimi Code while allowing users’ own logins, API keys, and custom providers.
- The desktop workflow is complemented by a JSON-capable CLI and a stdio MCP server for terminal and agent-driven operation.
- The documented release platforms are macOS and Windows x64; the supplied evidence does not document Linux support.
- Initial setup requires connecting GitHub or GitLab and signing in to at least one coding agent; the supplied material does not detail the authentication or permission model.
- Workspaces and data are local under `~/helmor/`; there is no documented evidence here of centralized deployment, shared team state, or remote workspace management.
- The mobile companion is explicitly experimental and uses a Cloudflare tunnel to reach the desktop.
- Slack and GitHub context, plan mode, and agent-driven orchestration are described as upcoming, rather than current capabilities.
How do you install or deploy this agent?
Download Helmor from GitHub Releases; the documented builds are macOS (Apple Silicon and Intel) and Windows x64. On first launch, connect GitHub or GitLab and sign in to a coding agent; the README states that agent CLIs are bundled. To install the CLI, use Settings → Experimental → Command Line Tool. For local source development, the documented commands are bun install && bun run dev.
How do you use this agent?
Add a repository, create a workspace, and send a task: helmor repo add /path/to/repo, helmor workspace new --repo myapp --name fix-auth, and helmor send --workspace myapp/fix-auth "Add tests for the token refresh path.". Check progress with helmor workspace status myapp/fix-auth, then use helmor workspace run-action myapp/fix-auth for an available shipping action. Workspace references use repo-name/directory-name; append --json to any command when machine-readable output is needed.
How does this agent compare with similar options?
Helmor is not presented as a replacement for Claude Code, Codex, Cursor, OpenCode, or Kimi Code. It is a local workflow layer that can connect those coding agents to isolated Git workspaces, review surfaces, and PR/MR actions.