Changelog
What changed in each Thrum release, and what to do when you upgrade: sync, backups, worktree folders and more.
If you are new to Thrum, start with the quickstart. These notes are for people upgrading from an earlier version. The glossary explains the terms.
Releases
1.0
The first release with Thrum Pro. Free still has everything your agents need to work as a team. Pro adds the web terminal, the Conversation tab that shows an agent's session as it works, the email bridge, the vault and more. One thing that was free in 0.10.5, the Conversations page, now needs Pro (see the upgrade notes). See [Free and Pro](/pricing.html#full-list).
thrum initasks how you use Thrum: open source, Pro, or Free (press Enter). Free sends nothing to Thrum's servers except a one-time install count, which you can stop.- New in Pro: the email bridge, which sends and receives Thrum messages through your own mailbox.
- New in Pro: email notifications.
- New in Pro: the vault, an encrypted store on your machine for the passwords and tokens your agents need. A secret you type at a terminal isn't shown.
- New: agent memory, notes your agents save and later sessions can search. Saving and editing memories needs Pro. Reading, searching and deleting them is Free.
- New: a watcher, an agent that checks on your other agents on a schedule. Ask your coordinator to start one.
- New: a record of what your agents did. The command log keeps every Thrum command, and the hook log keeps every tool call by agents on Claude Code, Codex, Cursor, OpenCode, Copilot and Muse. Ask your coordinator to search them.
- New: see how much of each AI tool's usage limit you have used. It is off until you ask your coordinator to turn it on.
- New: Antigravity works with Thrum through the Claude Code plugin.
- New on macOS:
thrum daemon launchd installkeeps Thrum running in the background after you log in. - Changed: Git sync is off unless you turn it on, and an idle machine no longer adds commits to the sync branch.
- Changed: on a new machine, pairing over the local network or Tailscale is off until you turn it on. Machines that already have paired machines keep it on.
- Changed: Thrum backs up your data every 24 hours by default.
- Changed: the Telegram bridge works in a private chat with your bot only. Group chats are no longer supported.
- Changed: Thrum no longer installs or runs Beads' hooks. Beads keeps its own setup.
- Changed: Thrum's plugins and Homebrew tap moved to github.com/thrum-team. Install Thrum has the new commands.
- Removed: the email bridge's multi-machine setup (
thrum email pair,list,revoke,rebindandunblock). Runthrum email initagain for the shorter setup. - New in Pro: answer an agent's permission prompt by replying to its email with approve, deny or a choice number.
0.10.5
Smaller commands, safer sends and a tidier setup when you already use Beads.
thrum inbox --from @agentshows unread messages from one sender.thrum worktree teardown --delete-branchremoves a worktree and its branch in one step.- The daemon now re-sends reminders for messages that stay unread. This replaces the old cron script, and it survives runtime restarts.
thrum sendnow needs a recipient. Without--to @agentit stops with an error. Before, it sent to every agent.thrum initmerges its hooks into an existing.claude/settings.jsonand keeps your own entries. Before, it skipped the file if it existed.- Beads is set up with
bd setup claude. Thrum does this for you whenbdis installed. - Worktrees no longer keep stale copies of the scripts Thrum manages for them.
0.10.4
A fix for commands that ran as the wrong agent.
- Commands that send, reply or mark messages read now stop with an error if you run them from a worktree that does not match your agent. Before, they went ahead as the wrong agent.
- Read-only commands such as
thrum teamandthrum daemon statusstill run from any worktree and print a one-line warning.
0.10.3
Codex support, more reliable agent startup and a fix for lost unread messages.
- Codex gets the same Thrum plugin hooks as Claude Code: it loads its briefing at session start and flags unread messages.
- An agent that sits idle after a launch or restart gets a nudge.
- Thrum no longer types into the first-launch trust prompt that Codex and Claude Code show in a new folder, so you can answer it yourself.
- Messages that arrive while an agent reads its inbox are no longer marked read before it sees them. The inbox also says how many messages a filter hides.
thrum initsuggests a lowercase default agent name, so the suggestion passes its own check.
0.10.2
Fixes for agent identity and for clean-up.
thrum quickstartaccepts registering the same name again, so a session start on an already registered worktree no longer fails.- New tmux sessions no longer pick up another agent's identity from the environment.
thrum purge --confirmnow shrinks the message files on disk. Before, it left them growing.
0.10.1
Two fixes to the 0.10.0 setup flow.
thrum quickstartrun in a worktree that shares another folder's settings no longer writes the agent's identity to the wrong place.- After a daemon restart, commands that write, such as
thrum send, no longer fail with "anonymous caller" in a worktree that already has a registered agent.
0.10.0
A guided setup and a new default folder for worktrees.
thrum initin a terminal now walks you through setup: agent name, worktree folder, role templates and starting the daemon. Flags such as--nameand--non-interactiveskip the questions for scripts.- A new
implementer-worktree-write-onlyrole template keeps an implementer's edits inside its own worktree. - The default worktree folder is now
~/.thrum/worktrees/<project>. See the upgrade notes below.
Upgrade notes
These notes cover changes that can affect an existing setup. Each one says which release introduced it.
One thing now needs Pro
In 0.10.5 the Conversations page, a one-to-one chat with each agent you have talked to, was free. From 1.0 it needs Pro. My Inbox and each agent's Messages tab stay Free, so you can still message every agent. Everything else you used stays on Free. Free and Pro has the full list.
Accept the licence once on each machine
The first Thrum command you run after upgrading asks you to accept the licence. Scripts, service units and agent sessions that cannot answer need the THRUM_ACCEPT_EULA variable set to the licence version, the one the licence notice prints. For this release that is 0.9.10.
THRUM_ACCEPT_EULA=0.9.10
Stop and start Thrum after installing
After you install the new version, run thrum daemon stop, then thrum daemon start, so the new version runs. A restart alone can start the old one again.
thrum daemon stop
thrum daemon start
Update your agents' instructions
After you install the new version and its plugin, run thrum roles refresh, then thrum roles deploy, so your agents' instructions match the new version. You may see a note that some roles have no model tier entry. It is safe to ignore: those roles use your default model.
thrum roles refresh
thrum roles deploy
The database upgrades on first start, with a backup first
When Thrum first starts on 1.0, it saves a backup of its database, then upgrades it. If the backup fails, Thrum doesn't start until you fix disk space or permissions. An older version can't open the upgraded database: to go back, restore the backup and install the older version. Memories saved after the upgrade are lost if you go back.
Update every machine together
Machines on 0.10.5 don't receive messages from machines on 1.0. If you share a project across machines, upgrade them all together.
Git sync is off unless you turn it on
If you relied on the old default, set the key to turn Git sync back on, then restart the daemon.
thrum config set daemon.sync_via_git true
Turn on pairing on new machines
On a machine with no paired machines yet, pairing is off. Turn it on in Settings, Pairing, or ask your coordinator. Work across multiple machines has the steps.
On macOS, move to the background service
If you restart Thrum from a cron job, remove that line from your crontab, then run thrum daemon launchd install.
thrum daemon launchd install
Install the plugins from their new home
Thrum's plugins now come from github.com/thrum-team. Install them again with the commands on Install Thrum. For Codex, update Thrum itself before the plugin.
Email bridge users: set it up again
Run thrum email init again for the shorter setup. The email bridge needs Pro.
thrum email init
Sends need a recipient
Scripts that ran thrum send with no recipient now fail. Name the agent with --to @agent in each command.
Move the standalone Beads plugin to Beads' own setup
If you installed the standalone Beads plugin in Claude Code, uninstall it, install bd, run bd setup claude and restart Claude Code. If you install or remove bd later, run thrum init again to refresh the hook.
Worktrees moved to a new default folder
New worktrees go in ~/.thrum/worktrees/<project>. If you set worktrees.base_path in .thrum/config.json, nothing changes for you. To keep using the old folder, ask your coordinator to set worktrees.base_path to it before the next worktree is created.
After any upgrade
Ask your coordinator to refresh the role templates and, if you use Codex, the Codex setup in your existing worktrees. The new version then installs its updated hooks and text there.