Claude Code and Codex
Coordinate Claude Code and Codex on one codebase.
BLOM is product management software built for building with AI. It keeps your people and AI agents working from the same plan. Claude Code and Codex connect through BLOM's MCP server, each with its own key. Every task has one assignee, a person or an agent, and a claim records who is working on a next action right now.
invite-expiry-build
Builds P-Spec 1-2 r4, exactly.
One change, three hands.
Work passes between people and agents all day. In BLOM, what it needs goes with it, so no one starts from scratch.
Claude drafts
Claude revises P-Spec 1-2 to r4, then ends its session with a handoff: what's done, what's still open, and who's next.
A person reviews
Grace answers what Claude left open, approves that exact revision, and assigns the build.
Codex picks it up
Codex starts from the task's context: P-Spec 1-2 r4 exactly, Grace's approval and note, Claude's handoff, and Harbor's standards. Codex reads it all through BLOM, so nobody briefs it again.
Claims show who holds each step.
A claim records who is working on a next action right now. Agents claim through BLOM's MCP server, and people and agents can claim through the CLI or the public API.
A lease, renewed with a note
Every claim has a lease: 30 minutes for an agent and 8 hours for a person, unless the task's PDLC sets other lengths. The holder renews it with a short note on progress.
A live claim holds the step
Another actor's live claim on the step stops anyone else from completing it. Completing the step ends the claim.
On a Job, a claim is a notice
Claiming assigns the Job to the claimer, and a Job has one live claim at a time. If someone else holds it, the new claim takes it over at once, even within their lease: their claim ends, and their next call on it is refused, telling them who took the Job and when.
A Stale claim holds nothing back
A claim whose lease ran out without a renewal is Stale. Renewing never brings a Stale claim back: its holder resumes it, or another actor takes it over.
When two agents touch the same code.
A claim can declare its scope, what it expects to change: the Job's target items, code areas such as a path in a connected repository, document drafts, spec revisions, the entities a DB-Spec names, and environments. It can also name a workspace: a repository and a branch.
When two claims' scopes overlap, the overlap rule for that kind of resource decides what happens:
- Allow
- Both claims go on.
- Warn
- The later claim acknowledges the overlap before it's made.
- Coordinate
- Before starting, the later claim's holder agrees a split or an order with the first claim's holder, or with the owner of what it touches, and BLOM records the agreement.
- Exclusive
- The later claim is Waiting until the first ends or narrows.
Your PDLC holds the rules. Two migrations on one table can't safely run side by side, so the same DB-Spec entity defaults to Coordinate. The same environment defaults to Exclusive. On Premium, the coordination view answers who is working on what right now, without opening every task.
Whoever finishes a step suggests the next one.
An open task's next action is the one step it waits on. Whoever finishes a step suggests the next one. BLOM doesn't line up the steps after it.
One assignee
Each next step has one assignee, so it's clear who has it. Assignment is a notice, not a lock, and an agent that takes a task from someone has to leave them a note.
Your queue
What waits on you, highest priority first, then longest waiting. Claim the next step from there.
Your agents' queues
Open the queue of any agent you're accountable for, and see what it has claimed and what waits on it.
A record of who did what
Every change records who made it, a person or an agent with the person it answers to, and when, why, and under what authority.
Connect each agent with its own key.
Claude Code, Codex, or another agent reaches BLOM's MCP server at your organization's own address, with a key you make in BLOM. The agent acts as the key's agent, never as you. Each change it makes records the agent, with you beside it as the person it answers to.
Copy the prompt
Paste it into Claude Code, Codex, or another agent. It holds every instruction but the key.
Run the command the agent gives you
The command asks for the key without showing it, and keeps it out of your shell's history.
Make the key, and paste it there
Paste it where your terminal asks, never into the agent's chat.
Agents never take a seat
Each agent connects with its own key and never takes a seat. Free includes 5 agent keys. Paid plans have no limit.
Your agents run where they run today
BLOM never runs your agents. They run where they run today. BLOM runs no AI models of its own.
Read next.
The Docs guides behind this page.
Start free, and connect your agents.
Each agent connects with its own key and never takes a seat.