Blume 2.0.24: Protect project settings and smoother chat starts
Protect project settings from agent edits
You can now stop AI agents from changing a project's settings in Blume, including its sources, applications, environments, name, and avatar.
On a project's Setup page, you will find a new Protect settings option, which is off by default. Only a person can turn this lock on or off; agents cannot change the lock.
When locked, Blume refuses any agent attempt to modify project setup and suppresses prompts asking agents to fix setup gaps. If an agent tries to make a change, Blume tells it not to retry and to ask you to unlock the settings if you want the change made. You can still edit project settings yourself while the lock is on.
Wait for the local agent connection before sending chats
In version 2.0.23, sending a chat right after opening Blume could fail with a message that Blume was still preparing your local agent connection.
Creating and sending owned chats now waits for your active workspace's connection setup to finish before dispatching the message.
- If your active workspace is already verified, it stays usable even if key setup fails for another workspace.
- If setup fails, the error appears in the chat composer so you can press Send again to retry.
Faster delivery history loading
Loading the full work-event history for a delivery now reads events in their existing index order instead of sorting them again in the database. This cuts the number of database rows read in half when loading delivery histories.
Try it
In this release
- #1640 Halve D1 rows read when loading delivery work events
- #1641 Wait for the local agent connection before sending owned chats
- #1591 Protect project settings from AI edits