Connect your agents
Install the plugin into Codex or Claude Code. Every conversation connects on its own.
Blume turns agent work into outcomes with evidence, and one human decision. Agents plan, build and test. You review the evidence and approve the revision.
LESS CHECKING IN
Blume follows every session for you.
FROM BRIEF TO MERGE
Blume follows every session for you. Each change, from the first instruction to the merged commit.
Works with
+ any other harness
As agents produce more code, the hard part is keeping their work visible, trustworthy and reviewable.
Know what every agent is doing and what is left before you ship. Today, that means piecing together terminals, chat logs and branches.


An agent saying “done” is only the beginning. You need evidence that the change works and meets your team’s definition of done.
Several agents can build at once. Your attention is still finite. Bring the work and its evidence together so you can make one clear decision.

Agents run the loop. Blume keeps the record. You step in when there is a verified revision to approve.
One product change with its brief, task tree, agent runs, code revision, tests and screenshots, intact from the first instruction to production.
Interactive product preview · Illustrative data
The process tells agents what “done” means, and every claim arrives with its evidence.
Agents work longer without supervision, and several can work in parallel without silent collisions.
How The delivery model lets agents coordinate, and the agentic loop lets the agent catch issues before involving you.
Every claim has evidence tied to a specific revision. You see what’s left at a glance.
How Evidence is pinned to the exact task, delivery and commit. Visual verification at zero friction.
Acceptance criteria become tests before review, and suites rerun before every review.
How Bug reports are reproduced with a failing test first, then fixed and rerun.
Download Blume, connect your agents, and review the evidence.
Install the plugin into Codex or Claude Code. Every conversation connects on its own.
Your agents plan, build and test. See what’s left at a glance.
Review test steps and screenshots. Approve the revision you ship.
A shared, versioned domain model gives every agent the same language, rules and edge cases. Each session starts with your team’s context, not a blank slate.
Your product’s working knowledge One model, shaped by real work
Entities, relationships and the words your team uses
Business invariants, permissions and boundaries
Critical paths and their expected outcomes
Known edge cases across time zones and currencies
Conventions and patterns agents must preserve
Reviewed decisions, findings and bug reproductions keep it current as your product changes.
Write acceptance criteria in the language your team uses.
Follow existing business rules and architecture boundaries.
Catch permission gaps, currency mistakes and dates shifting across time zones.
Download Blume and know what your agents built.