v0.1.15 · Windows, macOS, Linux · free in early access
A cockpit for your fleet of Claude Code agents.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.
Add rate limiting to the webhook intake — it fell over twice this week.
Message the agent in api… (/ for commands)
opusxhighen8%⏎ send · ⇧⏎ newline · ⌘V pasteSend
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.
Link a task
DETAILS
Repositoryapi
Branchmaster
Modehook-only
Started2m 40s ago
Last eventasked a question
ECONOMYthis agent
Context8% · 82k / 1.0M
Last turn143k tok
From cache56%
Turns replayed from disk carry no cost, so the totals here read low on purpose.
SHIP IT0 files
Branchmaster
Remotein sync
Uncommitted0 files
Review & commit
TerminalPorts 23Activityapi
FIRST RUNThree steps to your first reviewable diff — about four minutes.
STEP 01
Install and open it
One installer, no account, no sign-in. It finds the Claude CLI you already use.
$ winget install helmry
STEP 02
Point it at a repository
Pick a repo and an environment — local or WSL. Helmry creates the worktree per agent for you.
~/code/api → wsl:ubuntu
STEP 03
Start 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
ONE WINDOW
Not eight terminals. A fleet.
One agent in a terminal is a tool. Five agents in five terminals is a mess. Helmry gives the fleet a shape: who is working, who is blocked, and whose work is ready to ship.
12+
AGENTS AT ONCE
1
WINDOW
0
SERVERS
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 diff209
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−0
+ 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
5 agents in parallel209 ready for review0 serverszero third-party scriptsgit worktrees, isolatedyour keys never leave the machine5441 tests greenWSL + macOS + Windows5 agents in parallel209 ready for review0 serverszero third-party scriptsgit worktrees, isolatedyour keys never leave the machine5441 tests greenWSL + macOS + Windows
THE TRUST BOUNDARY
Everything above the line stays here.
Helmry is a desktop app, not a service. The case for it is built on what is not there — no backend, no telemetry, and none of your credentials on anybody else's server.
YOUR MACHINE
Helmry cockpitdesktop
agents × worktrees
12 running
your repositories
5 local
terminals & ports
wsl:ubuntu · zsh
your credentials
OS keychain
ONE WIRE CROSSES
claude
your own process · your credentials → Anthropic
Anthropic bills you directly. Helmry never sees a token of it.
WHAT ISN'T THERE
Helmry server
does not exist · 0 connections
✕account · sign-in · sync
✕telemetry · crash uploads
✕third-party scripts on this page
1OUTBOUND CONNECTION
0CREDENTIALS STORED BY US
0THIRD-PARTY SCRIPTS
100%CODE STAYS IN YOUR WORKTREES
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
The app does not phone home, and this page loads zero third-party scripts. Counting happens at the edge, without your data.
Windows 10+ · macOS 14+ · Linuxgit 2.30+your Claude Code subscriptionWSL execution environments
PRICING
Free while it's early.
Every feature, no caps, $0 during early access. Paid plans come later — with notice, and never mid-flight: work that's already running is never interrupted to make a billing point.
Nothing is taken away mid-flight
A limit is refused at the door, never applied to an agent that is already running.
The licence check is offline
A signed key verified on your machine — no activation server in the boot path, ever.
Free stays useful
When paid tiers land, a lapsed licence degrades to the free tier — it never bricks the app.
·Helmry does not include a Claude subscription — you bring your own; Anthropic bills it separately.
·Agents edit files and run commands on your machine.
·Works with Claude Code. Not affiliated with or endorsed by Anthropic.
EARLY ACCESSv0.1.15
$0/ month, per person
Paid tiers arrive after launch. Prices are not fixed yet, and you will be told before anything changes.
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.
Will the free tier disappear?
No. Paid tiers add capacity; the free tier keeps the cockpit usable.
HANDS ON THE KEYBOARD
A fleet is navigated, not clicked.
Every surface answers to the keyboard: jump between agents, walk a diff file by file, approve a command, send a reply — without reaching for the mouse.
⌘Ksearch agents, files, commands
⌥ ↑ ↓move through the fleet rail
j / knext / previous changed file
vmark a file as reviewed
⌘ ⏎send the message
⌘ ⇧ Papprove the pending command
v0.1.15 · released 3 days ago · 42 MB
Put your fleet on one screen.
Download, point it at a repo, start an agent. The first diff is minutes away.