v0.1.16 · Windows, macOS, Linux · first month free

A cockpit for your fleet of Claude Code agents.

Run a dozen agents at once — each on its own repo, branch and worktree. Helmry shows who is working, who is blocked on you, and whose work is ready to ship. All of it on your machine.

Requires your own Claude subscription — billed separately by Anthropic.

LIVE COCKPIT — CLICK AROUND
Helmry
✕
Helmry
Search agents, files, commands — or assign a task…CtrlK
live
New agent
Filter the fleet…
▾PINNED5
Redesign hero marketing site
helmry-sitemaster36m
working
working
Rate limiter for the webhook intake
apimaster2m
working
asks a question
Fix the flaky auth test
appmaster7h
working
needs approval
Migrate settings storage
desktopmaster5h
working
ready for review
Add mcp command support in chat
climaster7h
working
ready for review
▸WAITING ON YOU0
▸WORKING4
▸READY FOR REVIEW1
▸IDLE & RECENT4
Rate limiter for the webhook intakemasterwsl:ubuntuworking
Full auto
ChatChanges & reviewPreviewAPIActivity100Artifacts
Add rate limiting to the webhook intake — it fell over twice this week.
MD
opusxhighen8%⏎ send · ⇧⏎ newline · ⌘V paste
TERMINALPORTSACTIVITYapi · zsh
✓ bash · grep -rn "rateLimit" src/webhooks · 1.2s
✓ read · src/webhooks/intake.ts · 0.4s
✓ bash · git log --since=7.days · 0.9s
api › ? waiting on your answer▌
TASK
PAY-318 · Webhook intake keeps falling over — linked from Jira.
DETAILS
Repositoryapi
Branchmaster
Modefull auto
Started2m 40s ago
Last eventasked a question
ECONOMYthis agent
Context8% · 82k / 1.0M
Last turn143k tok
From cache56%
Spend is counted per agent, so the expensive one is visible before the bill is.
SHIP IT0 files
Branchmaster
Remotein sync
Uncommitted0 files
Review & commit
api
ONE WINDOW

Not eight terminals. A fleet.

One agent in a terminal is a tool. Eight of them in eight terminals is a mess — you spend the day polling windows to find out who needs you. Helmry gives the fleet a shape: one rail, one status per agent, one place to review.

12+
AGENTS AT ONCE
1
WINDOW
0
SERVERS OF OURS
01

Statuses that mean actions

The rail doesn't say what an agent feels — it says what you should do next. A question and a blocked command are different moves, so they get different colours.

workingleave it alone4
asks a questionanswer it1
needs approvalgate a command2
ready for reviewread the diff3
02

Review like a pull request

Work lands as a diff, per worktree, with one commit-and-push flow. You read code, not chat logs.

cockpit/commitStore.ts+96 −4
+ const rail = useCommitStore(rootKey)
− const [subject, setSubject] = useState()
+ rail.tick(env, path)
03

One worktree per agent

Own branch, own dev server, own tree — five agents build and rewrite at once, and your checkout is never touched.

~/.helmry/worktrees
├api@rate-limiteragent 2
├app@flaky-authagent 3
└desktop@settingsagent 4
your main checkoutuntouched
04

It has to pass before you see it

Point Helmry at your gates. A red one goes back to Claude with the output attached, and it fixes its own work.

✓typecheck0 errors
✓lint · formatclean
✓vitest5441 passed
✗check:copy1 violation
→ sent back to the agent, not to you
05

A whole board at once

Pin a Jira ticket to an agent and it knows what it is working towards. No cap on how many run in parallel.

PAY-318webhook intakeworking
WEB-77pricing page copyasks you
HEL-204settings storageready
DYN-8328hotfix rollbackqueued
4 of 12 tickets in flight
06

A real terminal underneath

Every worktree keeps a live shell, its ports and its environment. When you want the raw machine, it is one tab away.

app › npm test
✓ 5441 tests · 330 files
app › git push
PORTS
● :5173 vite · app
● :4321 astro · helmry-site
ENVIRONMENT
wsl:ubuntu · zsh
node 22 · git 2.43
HANDS ON THE KEYBOARD

A fleet is navigated, not clicked.

Jump to any agent, walk a diff file by file, queue a reply, stop a run — without reaching for the mouse. ⌘ is Ctrl on Windows and Linux.

⌘Kcommand palette — any agent, action or saved prompt
j / knext / previous changed file
vmark the file viewed
⏎send — or queue it while the agent is mid-turn
⌘ ⏎interrupt the turn and send now
Escstop the agent, keep what it did
THE TRUST BOUNDARY

One wire out. Everything else stays here.

Helmry is a desktop app, not a service. The case for it is built on what is not there — no backend of ours, no telemetry, and none of your credentials on anybody else's server. The sign-in it asks for is created and kept on your own machine.

YOUR MACHINE
Helmry cockpitdesktop app
agents × worktreeslocal processes
your repositorieson your disk
terminals & portswsl:ubuntu · zsh
your credentialsOS keychain
your sign-in~/.helmry
nothing above this line leaves the machine
ONE WIRE CROSSES
claude
your own process · your credentials → Anthropic
Anthropic bills you directly; Helmry never sees a token of it. The app's own traffic is an optional status.claude.com check and, if you set an update token, the update check on GitHub.
Two more only if you ask for them: Atlassian, when you connect Jira, and the relay you configure when you turn remote access on — it holds no key and stores nothing.
WHAT ISN'T THERE
Helmry server
nothing to sign in to · nothing stored
✕cloud account · cross-device sync
✕telemetry · crash uploads
✕third-party scripts on this page
1WIRE OUT — YOUR OWN CLAUDE PROCESS
0CREDENTIALS ON OUR SERVERS
0THIRD-PARTY SCRIPTS
0BYTES OF YOUR CODE WE CAN READ
No server in the middle

The desktop app talks to your repositories and your terminal. There is no Helmry backend to route through — and none to breach.

One wire, and it is yours

Your own claude process, authenticated as you. Anthropic bills you directly; we never see the traffic.

No telemetry, either side

No analytics, no crash uploads, no usage pings in the app — and this page loads zero third-party resources, fonts included.

WHAT IT NEEDS
Windows 10+ · macOS 14+ · Linuxgit 2.30+the Claude Code CLI and your subscriptionrepos inside WSL supported
FIRST RUNThree steps to your first reviewable diff — about five minutes. The full walkthrough →
01Install and open it

One installer, then an account you create on the machine itself — it lives in ~/.helmry, not in a cloud. Helmry finds the Claude CLI you already use.

Helmry-Setup-0.1.16.exe
02Point it at a repository

Pick a repo and an environment — local or WSL. Tick “isolated worktree” and the agent gets its own branch and checkout.

~/code/api → wsl:ubuntu
03Start agents and walk away

Give each one a task or a Jira ticket. Come back when the rail says a diff is ready.

⌘K new agent · assign task
PRICING

One plan. First month free.

Pro is $20 per person per month — every feature, unlimited agents and repositories. New subscriptions start with a 30-day free trial: cancel during it and nothing is charged. And billing never interrupts work: an agent that is already running always finishes its turn.

How billing works, in writing →
PROv0.1.16
$20/ month, per person30 DAYS FREEcancel during the trial — nothing is charged
Everything in the app, unlimited agents and repositories. Bring your own Claude subscription — Anthropic bills that separately.
Start your free month
one person, unlimited devicescancel anytimeyour code never reaches us
BEFORE YOU ASK
Do I need a Claude subscription?
Yes — Pro, Max or an API key. Helmry drives the CLI you already pay for.
What happens to my code?
It stays in your worktrees. Only what you send to Claude leaves the machine.
Is there a free tier?
No — Helmry is $20 a month, first 30 days free. Cancel during the trial and nothing is charged.
v0.1.16 · 13 Sept 2026 · Windows, macOS, Linux

Put your fleet on one screen.

Download, point it at a repo, start an agent. The first diff is minutes away.

Unsigned for now
SmartScreen and Gatekeeper ask once · why, and how to open it →
Needs git 2.30+ and the Claude Code CLI
Windows 10+ · macOS 14+ · Linux · repos inside WSL
Everything stays in ~/.helmry
one folder to back up, one to delete · your sign-in lives there too

Requires your own Claude subscription — billed separately by Anthropic. Agents edit files and run commands on your machine.