Repository navigation
Blume.codes - Turns coding agent sessions into better rules and skills #43427
Replies: 1 comment
|
One privacy detail would help me evaluate this before pointing it at real sessions. The post says no chats or code leave the machine, while your privacy page describes off-device processing for some features and a separate opt-in Cloud Improvements route. That section also says Cloud processing remains unavailable until the provider route and controls are verified, so I am not assuming it is enabled in the current release. Could you document the released behavior separately for local transcript storage, Connected plans, and Cloud Improvements? In particular: which process receives the excerpts, which model endpoint performs inference, what context is sent, and whether each mode is actually available. A harness running locally does not by itself establish that inference is local. If the intended guarantee is that Blume does not receive session content when using Connected plans, that narrower wording would be easier to verify. A useful acceptance test would use a disposable session containing a synthetic marker, then run each supported analysis mode while recording destination hosts and inspecting the constructed model request locally. Separately block non-loopback network access and check that a claimed local-only mode either completes locally or fails explicitly without switching providers. Please use synthetic data, not real session content, for any shared test artifacts. I reviewed the post and public docs only; I have not installed or tested Blume. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
https://blume.codes
We built Blume after our previous startup suffered severely from agent drift. Duplicated functions, incoherent architecture and sneaky production bugs.
We tried to control it with all the best practices: proper rules, skills, docs, self-verification. But when our repo grew, the setup rotted fast. Manual maintenance is too time consuming and asking the agent to maintain it lead to context drift and bloat.
Believing the true context signals lie in human intent, we had the idea to extract human intention and corrections from sessions and use them to improve the repo context. After initial testing, we were sure we were onto something, so we pivoted the entire company and built Blume.
Blume is a desktop app that sits next to Codex and learns from your sessions. Correction, nudges, frustrated ALL CAPS messages: Blume picks up on them and clusters them thematically. If a pain threshold or recurrence is reached, it suggests a concrete update to your setup. That can be updating a stale rule, patching a hook or skill, or creating an entirely new one. You review and apply it, improving the agent for the next run.
It is free to use, and uses your local harness for extracting and improving the setup. So no chats or code ever leaves your machine.
Try it now for macOS, Linux or Windows! And happy to answer any questions today on how it works or discussing approaches to giving agents proper up-to-date context
All reactions