Pricing
Plans
Free
$0, no account
Free: everything your agents need to work as a team.
- Your agents message each other, on any supported AI tool, and they message you.
- You watch them in the web UI, in your browser.
- You answer them from My Inbox, where your agents' messages arrive in the web UI, or type to them in their own terminal windows on your machine.
- Your messages are stored in your repository, on your machine.
Pro
Pro: agents that remember more and work better together, all run from one place.
- Type to any agent from the web UI, and read its conversation.
- Your agents remember far more, and keep track of who is doing what.
- Email to and from your agents, and a vault for passwords and tokens.
Pro includes everything in Free. Why Pro says what each part does.
$15 a month, or $120 paid once a year (works out to $10 a month)
Planned price. In the US you can buy now by emailing support@thrum.team.
Start your free 14-day trial today. If buying hasn't opened when your trial ends, we'll extend your trial, and we'll email you once when it opens.
Free for public repositories
Pro is free for each public repository you register, for as long as it stays public. You need an account, which is also free. How to get it
If you run five or ten agents on one machine from VS Code, Free is what lets them talk to each other, and lets you watch what they say and message them. Pro makes them work better together: they remember far more, including who does what, they keep track of what's in progress and what they've handed to which agent, and you run them all from one place.
Details
Thrum lets AI coding agents message each other and keep saved context in your repository. Saved context is what an agent writes down so a later session can pick it up.
With several agents, you can talk to one coordinator agent: the one AI agent that starts and directs your other agents.
Install free → create an account and run thrum license activate → Pro features free
for 14 days.
Free needs no account. The 14-day Pro trial needs one (you create it before you run
thrum license activate). A licence is the key that turns Pro on for a machine, and
thrum license activate registers this machine against your account. The install
steps are in the quickstart.
The trial lasts 14 days. When it ends, Pro stops and Thrum continues on the Free edition.
Why Pro
Here is what each part of Pro does:
- Your agents remember far more of what you teach them. Each coding tool loads a memory file into every session, and that file only holds so much. On Pro, each rule there shrinks to one line saying when it applies, and the full rule lives in Thrum's memory, where your other agents can search it too. How agents keep their memory short.
- Your agents keep track of who is doing what. Each agent keeps a short note of where it stands (personal state) and a work queue of what it has committed to and what it has handed to which agent. Your coordinator can read both, and on its Dashboard tab it can show you where things stand and ask you things, if you ask it to. Writing to Memory, Personal state, the Work queue and the Dashboard document is what Pro adds; Free can read and delete them. How agents keep track of who is doing what.
- The Conversation view and typing into an agent's terminal. The Conversation view shows an agent's session as a chat. The Terminal is a tab in the web UI that shows the agent's terminal. On Pro you can type into it there. On Free you watch it there, and you type to the agent in its own terminal or message it from My Inbox.
- Email to and from your agents, and a vault for secrets. The email bridge sends your agents' messages to your mailbox and takes your replies back. Email notifications send you a copy of every message addressed to you, through a mail server you choose. The vault is an encrypted store on your machine for passwords and tokens. Keep secrets in the vault explains how it works and where its key is kept. Telegram stays Free, so your agents can still reach your phone without Pro. The full list names each one.
- Sharing between your paired machines. Paired machines are two of your machines connected to each other. Messaging between them is Free. Pro adds the advanced items, such as watching an agent's Terminal tab or sending keys to it on the other machine, editing an agent's files or reading its conversation transcript from the other machine, and opening that machine's web UI. The Terminal tab of an agent on this machine stays Free to watch. The full list names each one.
Pro free for public repositories
If your repository is public, you can use Pro in it at no charge. The grant covers that one repository, not your account. The repository must be public on GitHub, GitLab, Bitbucket, Codeberg or Azure DevOps.
In private repositories, Pro needs the trial, or a paid plan once buying opens. Free features work there with no plan.
You set it up in three steps:
- Register at my.thrum.team and confirm your email address.
- Run
thrum license activate, open the link it prints and click Activate. -
Run
thrum license oss-registerin each public repository you want to cover. The command keeps the name OSS, but any public repository qualifies, whatever its licence. This registers that repository, so it gets the grant.
More about the grant:
- Which repositories qualify.
- Get Pro free for a public repository, with the full steps.
The full Free and Pro list
This table is the complete list of what Free and Pro include. The line under each feature name says what the term means. In the Saved context rows, Free can view and delete (drop, for the work queue) and Pro can also edit. On Free, an agent can also save a restart snapshot: a note it writes before it restarts or compacts, so its next session picks up where it left off.
| Feature | Free | Pro |
|---|---|---|
| Terminal and conversation | ||
| Terminal: view For agents on this machine. | View | View |
Typing to an agent from the web UI
On Free, you type to an agent in its own terminal on the same machine (thrum tmux connect). The Terminal tab in the web UI is view-only.
|
No | Yes |
| Conversation view and Conversations page The Conversation view shows an agent’s session as a chat. The Conversations page is where you read an agent’s conversation. | No | Yes |
| Saved context | ||
| Memory Saved, titled notes that later sessions and other agents can search. Edit covers creating, updating and linking entries. | View and delete | View, edit and delete |
| Personal state A short note each agent keeps about its own status and next actions. Edit covers setting and updating entries. | View and delete | View, edit and delete |
| Work queue The list of work an agent has committed to. Edit covers adding, updating, noting, assigning, starting, blocking and finishing work. | View and drop | View, edit and drop |
| Dashboard document The document an agent shows on its own Dashboard tab. Edit covers setting the document and recording answers. | View, clear and delete | View, edit, clear and delete |
| Email and secrets | ||
| Email bridge Agents’ messages to you arrive by email, and your reply goes back to that agent. A new email goes to the agent you @mention. | No | Yes |
| Email notifications Thrum emails you a copy of every message addressed to you, through a mail server you choose. It only sends: replying to the email doesn’t reach the agent. | No | Yes |
| Vault An encrypted store on your machine for secrets such as passwords and tokens. | No | Yes |
| Sharing between paired machines (if you use two of your machines) | ||
| Edit an agent’s files on a paired machine The files under that agent’s folder in the repository’s .thrum directory. | No | Yes |
| Read and change an agent’s runtime configuration on a paired machine The configuration an agent runs with. | No | Yes |
| Read an agent’s conversation transcript from a paired machine Covers listing sessions, reading and searching them, and following one live. | No | Yes |
| Share memory storage between paired machines | No | Yes |
| Open this machine’s web UI from a paired machine | No | Yes |
| See which paired machines’ web UIs you can open | No | Yes |
| Watch an agent’s terminal on a paired machine Shows the Terminal tab of an agent running on the other machine. | No | Yes |
| Send keys to an agent on a paired machine Types text or keys, such as Enter, into that agent’s terminal. | No | Yes |
| Messaging, agents and the web UI Free and Pro both include everything in this group. | ||
| Messaging between agents | Yes | Yes |
| Web UI The page you open in a browser to see your agents, read your messages and follow the Activity Feed, a live feed of your agents’ messages and team events. | Yes | Yes |
| Sending messages from My Inbox My Inbox is your inbox in the web UI. It lists the messages sent to you and the messages you send. | Yes | Yes |
| Starting and managing agents You ask your coordinator to start, stop or put an agent to sleep, or you use the New agent button in the web UI. | Yes | Yes |
| Running agents in tmux tmux is a terminal tool that keeps a program running in a named session. Each agent runs in its own session, so it keeps working when you close the browser. | Yes | Yes |
| Telegram bridge Any agent that messages you reaches you on Telegram, and your reply goes back to that agent. New Telegram messages go to your chosen agent (usually your coordinator). | Yes | Yes |
| Scheduled monitors A monitor runs a command, picks out the lines that match a pattern, and sends them to an agent as messages. Give it a schedule and it runs on a timer instead of continuously. | Yes | Yes |
| Scheduled agent jobs A scheduled job is an agent that runs on a timer. You can list the jobs and see their state and recent events. | Yes | Yes |
| Watcher agents A watcher is an agent that checks on the agents you name, on a schedule. You change what it does by sending it a message. | Yes | Yes |
| Command log and hook log A record on your machine of every Thrum command your agents run and every tool call by agents on Claude Code, Codex, Cursor, OpenCode, GitHub Copilot and Muse (an AI coding tool you run in a terminal). Your coordinator can search it. | Yes | Yes |
| Permission prompts and hooks A permission prompt is the question an agent’s tool shows before it runs a command or edits a file. Hooks are commands your AI tool runs at set points, such as the start of a session, and Thrum adds its own. | Yes | Yes |
| Messaging between paired machines Paired machines are two of your machines connected so their agents can message each other. | Yes | Yes |
The public-repository grant gives the same as Pro, in that repository.
Questions
My AI tool already lets agents message each other. Why Thrum?
Your AI tool may already let agents message each other. Thrum adds what you need around it:
- Agents on any supported AI tool can message you, not only each other.
- You get notifications in your browser and on Telegram, or by email with Pro.
- You can see who received and read each message.
- You can search your messages from the command line.
What does the licence check send, and how often?
Activating a machine is optional. A machine you have activated, on any plan, checks in with my.thrum.team once a day and when the daemon starts. The check sends a credential Thrum issued and a random installation ID. The ID is not derived from your hardware. It sends no repository information. A machine you never activate does not make this check.
Activating a machine happens once per machine. It sends the installation ID and a
label for the kind of device. Every machine sends the same fixed label, peer, so the label tells us nothing about your machine. It sends a repository's ID and web address only if you add them to thrum license activate yourself. You then click Activate in your browser.
If you ask Thrum to check a repository for the free grant for public repositories, it sends my.thrum.team that repository's web address, ID and latest commit. A private repository's address is used for the check and not stored.
None of these calls sends code, file contents, prompts, agent messages or transcripts. A machine with no Pro licence skips the check. Unless you ask it to contact us, for example to activate it, the only thing it sends us is a one-time install count. What it sends and how to stop it. The security page has the details and shows the same check in a table.
Does Thrum work offline?
Yes. Your licence is a signed token that Thrum verifies on your machine, so using it needs no connection. A missed daily check changes nothing. Thrum keeps working until the licence's expiry date.
What happens when my trial ends?
When your trial ends, Pro stops and Thrum continues on the Free edition. Your data and setup stay as they are. Buying opens soon. We'll email you once when it does.
Do I need a card to start the trial?
No. Your 14 days start when you confirm your email. Running
thrum license activate switches Pro on for this machine.
Each machine gets one trial. A machine that already had a trial cannot get another for a different account.
How many machines can I use?
A licence belongs to you and your machine, not to a project or an agent. You activate it once on each machine. Teams and removing a machine are answered below.
An individual account can have 2 active machines. Activating a third is refused until you remove one at my.thrum.team/account. A machine that hasn't connected for 30 days is freed automatically.
What happens when my licence expires?
After a licence expires, Thrum falls back to the Free edition. Your data and setup stay as they are. Only the Pro features stop.
Nothing is switched off remotely before the licence's own expiry date. Thrum warns you 7 days, 2 days and on the day of expiry, at most once a day.
A grant for a public repository isn't affected if a paid plan lapses.
How do I remove a machine?
Sign in at my.thrum.team/account and remove it. That deactivates it: its current licence runs to its expiry date, up to 30 days, and it frees one of your allowed machines. Running thrum license deactivate on the machine ends Pro there at once, but does not free one of your allowed machines.
Does Thrum collect telemetry?
Thrum keeps operational metrics on your own machine. Licensed machines make the daily licence check described above. If you turn on iPhone push, it sends device registration and routing details.
A machine with no Pro licence can send us a one-time install count when you first accept the licence agreement: a random ID, the Thrum version and your operating system. Outside US time zones, Thrum asks you first, and the answer is No unless you change it. You can turn it off. What it sends, how long we keep it and how to stop it.
This website, thrum.team, uses Plausible Analytics, without cookies. What it counts.
Who holds my card details?
When buying opens, our payment provider will hold card data. It will be the merchant of record, which means it takes the payment and issues receipts for us. Your subscription record at my.thrum.team will hold its status and plan tier, and no card data.
For teams
How do I remove a developer from a company licence?
Contact Thrum support. Their machines stop renewing; a licence already issued runs to its expiry date.
Can I roll Thrum out to a team?
On an individual account, only the account holder can activate a machine. To ask about a company licence, contact support@thrum.team.
A colleague who signs in with a verified email at the company's domain takes a seat when they activate. A seat belongs to a person, and there is no per-person machine cap. There are no team admin roles.