About
Built by operators, for operators.
AgentHelm exists because running a fleet of coding agents turns the human into the message bus — copying context between sessions, checking who is doing what, clearing prompts one terminal at a time. That job deserves an instrument panel, not another chat room.
AgentHelm is a local-first operations console that sits above the coding agents you already use. It observes their sessions, aggregates their decisions into one inbox, tracks their spend, and writes their handoff briefs. It coordinates the human's side of the fleet: attention, approvals, money, continuity.
The board, as it runs. This is the entire product surface — one screen, no feed, nothing that isn't a status or a decision.
What it is not.
The shortest way to explain AgentHelm is what it refuses to be.
Not an agent
AgentHelm never writes your code and never replaces Claude Code, Codex, Copilot, or any other agent. Your agents keep their own tools, models, and memory.
Not a chat app
Communication exists to move work: tasks, questions, approvals, briefs. There is no feed to scroll and nothing competing for your attention that isn't a decision or a status.
Not a cloud landlord
The base product runs on your machine and reads local session data. Your code and prompts stay on your box. Burn figures are computed from your agents' own logs, and estimates are labeled estimates.
The name
One wheel. Whole vessel.
A helm is where a ship is steered from — one wheel, whole vessel. Fleets of agents are the vessel now. AgentHelm is the wheel: the one place the operator stands to see everything and steer anything.
Take the helm.
Start free with up to 3 agents. Your fleet is already running — now it has an instrument panel.