Build
Coding sessions in your own repo, on your own plan.
Build runs Claude Code, Codex or DeepSeek in the working folders on your Mac. It reads your repository’s own instructions, follows the plan task it was given under your git rules, and stops when a decision is yours.
How it works
- 1
Pick a folder
Choose a working folder on your Mac, or let an Initiative start a Build for one of its plan tasks.
- 2
It reads first
Your CLAUDE.md and AGENTS.md, the repo’s MCP servers, your operating rules and the approved design all load before it writes anything.
- 3
It builds and asks
Work streams in as it happens. A question or permission request appears as a card and waits for your answer.
- 4
It reviews and hands back
A fresh session reviews the diff against the plan and fixes what it finds before the Initiative hears the Build is done.
Your subscription
Your plan, your machine, your code
Build drives the Claude Code or Codex CLI you already have logged in, or a DeepSeek model on your own key. Your code stays in your folders, and there is no token bill from Boardbox.
- Billing stays on the account you chose
- A preflight check names the fix when a CLI is missing or logged out
- Your personal CLI settings and servers stay out of the session
Rules
Your git rules, enforced
Write your git workflow once. For Claude Code, Boardbox compiles it into permission rules and a command guard, so a forbidden push is blocked before it runs.
- Control commits to the default branch, force pushes, history rewrites and branch deletion
- Your repository instructions load beneath your operating rules
- Skills are packaged into each session, read only when the work calls for them
Initiative Builds
Built from the plan, reviewed before it is done
An Initiative hands each Build one locked plan task and the exact design version you approved. Effort follows the work, and a fresh session that never saw the reasoning reviews the diff at the end.
- Departures from the plan are recorded in a deviation note
- Simple tasks run fast, hard tasks think longer, stalled tasks get more effort
- The review fixes security flaws, regressions and missed edge cases
Where it stops for you
Runs on its own
- Reads the repository and plans the change
- Edits files and runs your tests in the working folder
- Moves its plan tasks forward and keeps going between turns
- Reviews its finished diff in a fresh session
Waits for you
- Questions only you can answer, as a durable card
- Permission requests Claude Code escalates
- Work outside its plan task, which goes back to the Initiative
- Pushing and merging, which stay with you
What it works with
Reads
- Working folders
- CLAUDE.md and AGENTS.md
- The repo’s MCP servers
- Operating rules and skills
- Approved designs
- Library
Produces
- Code changes
- Commits under your rules
- Task progress and deviation notes
- A context receipt for every run
Where founders use it
Shipping a feature from a design
The Build implements the exact approved handoff, so what ships is what you signed off on.
Fixing a reported bug
A support investigation becomes product work with its evidence attached, and a Build fixes it in the real repo.
Working by hand
Open a Build on any folder and pair with it directly. It still knows your company, your rules and your design system.
How it compares with a coding agent in your terminal
In the Tablebird launch
Built from the version she approved.
A coding session on Ava’s own Claude Code or Codex plan builds it in the real repo, and stops when a decision is hers, like who should be allowed to export payroll.
Follow the whole launchWhat people ask
- Which engines does it support?
- Claude Code and Codex on your subscription, and DeepSeek on your own API key.
- Can I use Build without an Initiative?
- Yes. Start a Build from any working folder and work with it directly, then mark it complete when you are done.
- Do I choose the reasoning effort?
- No. Boardbox picks it from the task’s difficulty and raises it when a turn stalls. A one-turn Think harder is there when you want it.
- Does my Mac need to stay on?
- Yes. Builds run on your Mac, so the desktop app needs to be running. A disconnect interrupts the turn instead of replaying it.
- What does Boardbox see of my code?
- The session runs locally against your folders. Business credentials never reach the CLI.
How it connects to the rest of the company
Every capability reads the same Library and reports into the same Initiatives.
Early access · macOS
Run your next launch from one conversation.
We’re onboarding a few founders and small teams each week, one at a time, starting with the launch you’re planning next.
We email you once, when your seat is ready.