Integrations
HiveBase with Claude Code and Codex
How HiveBase works with Claude Code and Codex — they build in the lanes of a Mission on your own plans, and ask HiveBase for company facts over MCP.
HiveBase with Claude Code and Codex. They are the builders you already chose, on the plans you already pay for. HiveBase is the job around them: a plan, an independent check, and a receipt. It does not replace either agent, and it does not ask you to pick between them.
Two things connect them, and they are independent:
- A Mission uses them as builders. HiveBase hands each lane of a Mission to Claude Code or Codex and runs the CLI on your Mac.
- They ask HiveBase over MCP. Inside their own sessions, in your own terminal, they can look up what your company has already decided.
A Mission uses them as builders
A quick task runs as one focused agent. A big one becomes a Mission: the Lead plans it, splits it into lanes, each lane goes to the right agent, the work is checked, and it lands for you to review.
- 01PlanThe Lead reads the task and your repo
- 02LanesSplit across Claude Code and Codex
- 03BuildEach CLI runs on your Mac
- 04CheckAn independent check against the plan
- 05ReviewA draft pull request and a receipt
- 01
Plan
The Lead reads the task and your repo
- 02
Lanes
Split across Claude Code and Codex
- 03
Build
Each CLI runs on your Mac
- 04
Check
An independent check against the plan
- 05
Review
A draft pull request and a receipt
- The Lead plans and splits. The Lead is HiveBase's planner for a Mission. It breaks the work into lanes and decides which agent each lane goes to.
- Each lane is routed on its own. One Mission can put Claude Code on one lane and Codex on another.
- Your plans do the work. Runs go through the CLI you signed in, on your Claude or ChatGPT subscription, and use that plan's allowance.
- On your Mac today. Missions run on a Mac that is awake with HiveBase Desktop open. HiveBase Cloud is rolling out. The setup guide covers installing both CLIs, signing them in, and starting a first Mission.
- You review what lands. When the work checks out, the Mission opens a draft pull request, or hands off the branch, for you to review and merge on GitHub.
The independent check and the receipt
The agent that builds a lane is not the one that decides it is done. After the build, an independent check grades the work against the plan. A passing check is evidence for your review, not a replacement for it. When the check finds a problem, the Mission can send the lane back to be repaired and checked again, within bounds, before the result reaches you.
The result comes with a receipt: what was built, what the check found, and where the work stands. See Coding tasks & verification for the verdict labels and Action receipts for what a receipt records.
They ask HiveBase over MCP
Separately from Missions, Claude Code and Codex can connect to HiveBase as
ordinary MCP clients at https://mcp.hivebase.ai. Connected, either one can
read the source-backed company context HiveBase holds: current decisions, what
changed, and the open work on the board.
The install commands for Claude Code and Codex are in
Connect over MCP. Sign in with browser OAuth, choose the
workspace, then ask the agent to call context.brief.
Useful calls once connected:
context.brief— the company primer, the same payload every connected client gets.decision.search— look up what the company already decided before the agent decides again.task.searchandtask.get— read current work from the shared board.
Reads are free. Writes are scoped, held for confirmation over OAuth, and carry who wrote them. Every tool and scope is in the MCP tool reference.
CLAUDE.md and AGENTS.md stay yours
Many repositories already keep rules for these agents in CLAUDE.md and
AGENTS.md. HiveBase can keep one marked block in those files true, without
taking the files over.
When you confirm a correction that replaces a fact those files depend on, HiveBase opens a pull request that refreshes the block. You review it and merge it like any other change. The block is marked, so you can edit around it or delete it, and you keep everything if you stop using HiveBase.
Scope of the refresh
The pull request follows corrections that replace an existing fact. A
brand-new fact reaches agents immediately through context.brief over MCP,
but it does not open a pull request against the files.
When not to use this
- You want one agent in one terminal on a small change. Run Claude Code or Codex directly. HiveBase adds nothing you need there.
- You need the Mission to keep going with your laptop closed. That is HiveBase Cloud, which is rolling out. Until it reaches your workspace, a Mission needs your Mac awake.
Related
Set up for local Missions
Install Desktop, sign in both CLIs, run a first Mission.
Connect over MCP
Endpoint, install commands for each host, and the tool catalog.
Coding tasks & verification
The check, the verdict labels, and what stays gated.
Connected agents
Delegating a coding task to an external agent.