Blume is beautiful. I need to know where the agents live.

What I tried

Blume’s first screen did something unusual: it made me look straight at the center. On my large display that was almost too effective. I felt dizzy, came back to it several times anyway, and then moved the page to a smaller screen. Much better. Further down, flowers and branches connect the different parts of the product as I scroll. That motion is beautiful, and it gives me time to understand what Blume is for. It watches the rules, skills, hooks and hidden files around coding agents, then puts their state and changes in one sidecar. The page names Cursor, Claude Code, Codex, omp and Pi, and shows Agents, Setup, Usage and Improve views. That is close to the window I want beside my work.

Where I got stuck

My hesitation is about the word local. I am running Codex, ZCode, Kimi and Devin across my Mac and a remote Linux development machine. I want one place to see which agent is working, which one needs attention and what changed, while the conversation and project data stay under my control. Blume’s privacy page says supported transcripts are stored in a local SQLite database, and that usage and spending are shown locally from provider accounts. It also says some features can send relevant conversation excerpts to cloud AI models, with Cloud Improvements requiring an explicit choice. That is a reasonable disclosure, but it is not yet the guarantee I need. I have not installed the app or verified how a remote machine connects, whether Tailscale can remain the bridge, or whether the data from each machine stays local rather than passing through a Blume account.

One thing I'd change

I would make the multi-machine privacy boundary impossible to misunderstand. Show a concrete diagram for Mac plus remote Linux: what is read locally, what is stored where, what crosses the network, and which connection methods are supported. A short example using an existing private link such as Tailscale would answer the question better than another feature card. Also, let visitors preview the first screen at a calmer scale; the large-screen hero is visually striking but physically uncomfortable for me. The flowers below can keep doing their work.

Would I pay

Yes, if it can bring my local agents together without turning their state or work into cloud account data. I would pay for a clean view across my Mac and remote development machine, with the existing connection method staying in control. The product already feels valuable; local-only operation, or a precise and trustworthy explanation of the few exceptions, is the condition.

■

Roger HE is building PersonWise — The presentation presents itself.

Respond to this review →