Stop babysitting your coding agents. They check each other's work, so you can trust what
reaches you.
Your agents message each other, even when they run on different tools: Claude Code, Codex,
Cursor and more. No more pasting one agent's answer into another's window. Start with two: a
coordinator you talk to, and a reviewer it creates when you ask. When the work grows, add
agents and keep talking to one. You get decisions, not diffs to chase.
Start your free 14-day trial today. Buying opens soon. We'll email you once when it does. No card for the trial. When it ends, Thrum goes back to Free and your data stays.
Free costs nothing and needs no account: your agents message each other, you talk to them in their
own terminals or message them from My Inbox, and you watch them in the web UI. Pro is
$15.00/month or $120.00/year. It lets you type to your agents from the web UI and lets them
write memory and a work queue.
You type one request to your coordinator. It hands the work to Codex. A reviewer on a
different model checks Codex's work, and the coordinator approves the reviewer's
permission prompt for you. Then you get a report to decide on. The walkthrough is
narrated and just over two minutes; it opens with a short look at the console.
Here the coordinator is set to ask you before it merges. By default it merges routine
changes itself. Agent work is sped up in places. Recorded with Thrum Pro, which adds the
work queue the coordinator uses to keep track of your request. Captions are available.
Agents check each other's work
An agent saying "done" is a claim, not a result. In Thrum, the claim is checked before it
reaches you.
Your coordinator reviews each branch, and before it pushes a merge it's set up to build and
test the merged result. You choose whether it asks you before each merge or merges
routine changes itself.
Add a gate agent, an agent whose job is to run your tests on that merged code. Its verdict says what it
measured and what it didn't. If no gate agent checked a merge, the record says so.
The agents that write the code (implementers) are told to start from a failing test, so a fix has
something to prove.
In the video above, a reviewer on a different model reports two minor findings, and the
coordinator confirms neither needs a change before anything reaches you.
If you run more than one coding agent
You don't need several agents already. Two are enough to start, and each one can run on
whichever AI tool and model you choose.
You're the one carrying messages between them, checking what each one says it did, and
remembering who is waiting on whom. With Thrum, they message each other, a reviewer checks
what they say they did, and you talk to one coordinator.
Thrum is for developers running more than one coding agent on real code, who want to stay the
one who decides. With two or three agents, Free has everything your agents need to work as a
team. It costs nothing and needs no account. If your project is in a public repository, Pro is
free too, for each one you register, as long as it stays public. You need a free account for
that. How to get it
Many AI tools let one agent hand work to its own subagents or team. Thrum's messages go
between full agents, each in its own session, on whichever supported tool it runs, and to you.
If one agent and its helpers cover your work, you may not need more. Thrum is excellent when
your agents run on more than one tool, or when you want one coordinator to talk to and an
inbox of your own.
If you'd rather not build it yourself
If you want this functionality, you can build it yourself today. Claude Code is good at that,
but you have to build it yourself, and you have to troubleshoot it. Thrum gives it to you out
of the box, and that part is free.
Ask your coordinator to add a deployer. It runs your scripted deploys. It's set up to deploy
dev and staging on its own and to ask your coordinator before production. Afterwards it
checks the deploy and reports back. Your AI tool runs your own deploy commands and cloud
tools.
When your AI tool asks permission to run a command, Thrum tells you. Answer from the web
inbox or Telegram, which are free, or by replying to an email with Pro. Thrum types your
answer into the agent's terminal.
What Thrum takes off your plate
Answer your agents’ questions once, from one place
Write to your coordinator in plain words and it passes your request to the right agent. It answers what it can and brings you the questions that need your decision, and your answer goes back to the agent that asked.
When an agent stops to ask permission, Thrum sends the question to your coordinator and, if you choose, to you. Reply approve or deny and Thrum presses the key for you.
I started Thrum because I was the bus between my own agents. I'd read the message in pane 1,
switch to pane 3, summarize, hit enter. Forty seconds, fifty times a day.
Now I build Thrum with Thrum. My agents have sent each other over 650,000 messages in five
months, across the 8 machines I build Thrum on.
Counted from my fleet's message store, October 2026.
My coordinator does the merging, and brings me in when there's doubt. I decide what ships.
I don't see nine merges out of ten. On my fleet, every merge also gets a philosophy check and
a hot-path check plus a race gate run when it matters. Trust but verify is a real thing.
Leon Letto
Start with two agents, add more only when you need them
Install Thrum. You do this once per machine.
Create your coordinator. A short setup wizard in your repository asks a
few questions.
Talk to it. Ask it for a reviewer first. After that you write to your coordinator in plain words.
Grow it when the work grows. You still talk to one coordinator. Add only what
you need:
An orchestrator, for work with several steps or branches. It briefs the implementers
(the agents that write the code) and checks their work, so your coordinator stays on
decisions.
A gate agent, to test each branch merged with everything else before it lands.
You make the decisions. The agents do the checking.
Thrum doesn't call any AI model itself. Every token is spent by your agents, in the AI tools
you already use. Each agent you start reads a briefing and a set of skills first, and the
messages that keep your agents working together add some usage too. Reviewers and gates use
tokens only when you start them. You decide how many agents run. That's the cost of agents
that check each other's work.
If you've tried other tools for running many agents and found them a lot to run: with Thrum
you start with one coordinator and add roles only when the work needs them.
Start your free 14-day trial today. Buying opens soon. We'll email you once when it does. No card for the trial. When it ends, Thrum goes back to Free and your data stays.