It reads before it proposes
Every round starts in the code. The manager knows what exists, what shipped last and what is half-finished.
Bring a rough idea. The project manager works out the rest.
Give an AI project manager a repository or one blunt sentence. It decides what to build, in what order and how, then keeps handing work to a designer and up to twelve AI developers. You are the CEO: approve, reject, or step out.
Get Booardroom on GitHub
Meet the manager
macOS, Windows, Linux
YouChief Executive
Project ManagerReviewing
DesignerIdle
Ada
Linus
Grace
Dennis
Barbara
Ken
Margaret
Alan
Edsger
Radia
Donald
Katherine
Waiting for you
Board
Project Manager proposes SmallDesigned
Undo for deleted invoices
A deleted invoice is gone for good today. A 10-second undo saves the support ticket.
ApproveReject
Approved
Queued
Building
BR-21 · AdaCSV export for reports
BR-22 · GraceRecurring invoices
BR-23 · DennisPDF themes
BR-24 · KenTax rates per client
BR-25 · RadiaClient portal login
In review
BR-20 · LinusDark mode
Shipped
BR-19Onboarding checklist
BR-18Invoice numbering
It thinks for itself, and it does not stop.
Most agent tools wait for your next prompt. This one has a manager whose job is to have the ideas. You set the direction once. The manager owns the roadmap from there.
What you write, once
A tool for freelancers to send invoices. Make it good.
You, Chief Executive
What the manager comes back with (example)
- Round 1Smallest version that sends one invoice
An empty repository gets a running core first: one client, one invoice, a PDF.
- Round 1Invoice numbering that survives deletes
Tax offices expect gapless numbers. Nobody asked for this. The manager raised it.
- Round 2Late-payment reminders
Proposed after reading what round 1 shipped and seeing due dates had no follow-up.
- Round 3Recurring invoices for retainers
You rejected a dashboard with the note "too early". The manager changed course.
It decides the how, too
Each idea arrives as a work order with the architecture decisions already made: data shapes, files to touch, how to verify.
It keeps coming back
When the board runs low, it drafts the next round. Your rejections, and anything you tell it in conversation, shape what comes next.
From idea to shipped, and only one step needs you.
- 01
The manager proposes
It reads the repository and your brief, then writes work orders with the architecture already decided.
- 02
The designer specs it
Anything a person will see gets a design spec first: layout, every state, exact wording, the tokens to use.
- 03
You decide
Approve or reject from your Desk. A rejection can carry a reason, and the manager reads it before the next round.
- 04
Developers build
Free developers pick up tasks in parallel, edit files, run the tests and commit. A blocked command pauses and asks you.
- 05
The manager reviews
It checks the diff against the work order and the design. Approved work is pushed to GitHub.
Switch on autopilot. Keep a hand on the brake.
On autopilot the manager's proposals go straight to the developers. Left alone, agents would run until your Claude limit. Four brakes stop them first.
Agents' share of your 5-hour window
6.0% of 10%
Claude Code reports how full your subscription window is after each run. Booardroom reads that number and holds new work once the agents have used their share.
- 10%
- Share of the window. Agents stop after burning this slice of your 5-hour or weekly limit.
- 80%
- Ceiling. Agents stop once the window is this full, your own usage included, so you keep room to work.
- 10 / day
- New tasks per project. The manager stops proposing when the day's quota is used.
- 2 rounds
- Review limit. After two failed reviews the task leaves the loop and lands on your desk.
Those are the defaults. Each one is a setting.
Built for running real repositories.
Talk to the manager
Tell it a rule, a wish or a change of mind. It answers, briefs the developers and the designer, and queues the work.
Chat archive
Past Claude Code sessions on your machine show up on their own. claude.ai chats import from a data export.
Handovers
Hand an old chat to a project. Claude compresses it into a brief the team reads before each run.
Your permissions, inherited
Developers may run what you already allow Claude Code. Anything else pauses the task and asks you, with one press to allow.
Stays on your machine
The server listens on localhost only. Projects, tasks and logs live in one SQLite file in your user folder.
Desktop app
One window for macOS, Windows and Linux. The browser version runs from the same code.
Agents invent package names. Attackers register them.
The attack is called slopsquatting: a model suggests a package that sounds right, someone has already published malware under that name, and an unattended agent installs it. Booardroom checks every package before any agent installs it.
$ npm install express react-pretty-state slopsquat-guard blocked this install. BLOCK react-pretty-state: does not exist on the registry (likely a hallucinated name) Do not retry with another guessed name. Find the real package in the project docs or on npmjs.com.
- Blocked
- The name does not exist. The install is refused and the developer is told to find the real package.
- Asks you
- It exists but looks wrong. New on npm, almost no downloads, or one letter away from a popular name. The developer stops and you decide.
- Always on
- The model cannot skip it. The check runs in front of every shell command, for every agent, on npm, pnpm, yarn and bun.
The check is slopsquat-guard, our own open-source plugin for Claude Code. It is one layer of defence. It does not read package source code.
Each project gets a manager, a designer and up to twelve developers.
Free for personal use, and on GitHub.
$ git clone https://github.com/GracjanFilipek/Agent-Corp.git booardroom $ cd booardroom $ npm install $ npm run app # or try it with canned agents, no Claude calls $ npm run app:demo
- Node 22.13 or newer. The server has no other dependencies.
- Claude Code, logged in. Agents run as
claude -punder your own login, on a Pro or Max plan or an API key. - A folder to work in. Point a project at a repository, or let Booardroom create an empty git workspace.