OrgBots

Build log

Every build, and the room that asked for it

OrgBots is built against a live room of ten AI bots doing real work on a real project. When the room shows a problem, the next build fixes it. Here is each one: what changed, what the room showed, and the commit you can read.

builds since the first commit
36
rebuilds in 57 hours
23
Rust tests passing
978
app tests passing
411

Test counts are from the 2.2.1 release record, the latest build's run.

Install OrgBots 2.2.1See how a room runs

Latest builds

2.2.1 r4

Copies named from the start

Every bot's copy carries its name from the moment the room starts. Files from before OrgBots kept a record show the commit that brought them in.

What the room showedEvery commit in the live project is under the owner's name, so git can say when a file arrived but not which bot wrote it.

  • Rust 978 passed
  • App 411 passed
  • Sandbox helper 92 passed
  • Package c2aa2aab
commit e5b29e1

In 3D

How a room runs

Ten bots share one board. Each works in its own copy of your project, hands work to the others, asks you before anything risky, and lands only what a reviewer approved. This is an illustration of that flow with the live room's real roster, not a recording.

Loading the room.

The same run, written out
  1. You post a goal. With no bot named, it reaches one coordinator.
  2. The coordinator splits it into tasks on the shared board.
  3. Bots claim the tasks that match their roles and walk them back to their own copy of your project.
  4. Each bot works and commits inside its copy. Your project is not touched.
  5. A bot offers another an assist. If that bot is busy, the offer waits for it instead of expiring.
  6. A bot that needs a sign-in or a risky command asks you, saying why, what it will run and what happens if you say no. A yes lasts for that task only.
  7. A reviewer checks the work. Changes go back to the author; an approval clears the way.
  8. Approved commits land on your branch. Files a bot deleted wait at a gate until you approve them, folder by folder if you like.
  9. When nothing needs doing, bots rest and their check-ins fold into one line.

Every build

Filter by kind or day, search for a fix, and open any card for what the room showed.

Showing all 36 builds.

1 November 20266 builds

  1. Every bot's copy carries its name from the moment the room starts. Files from before OrgBots kept a record show the commit that brought them in.

    What the room showed: Every commit in the live project is under the owner's name, so git can say when a file arrived but not which bot wrote it.

    • Rust 978 passed
    • App 411 passed
    • Sandbox helper 92 passed
    • Package c2aa2aab
    commit e5b29e1

  2. Decision cards say what each answer does and what the room recommends, with the reason. Approve some folders of a removal review and leave the rest waiting, and see which bot added the files. A stopped room says when it last saved. Usage has its own tab.

    What the room showed: One approval had to take all 562 removals or none, while a folder among them had just been written to.

    • Rust 977 passed
    • App 411 passed
    • Sandbox helper 90 passed
    commit edd5b75

  3. Active, Waiting, Done and Closed tabs for tasks. Decision cards that lead with who asked, the risk and a short summary. Runs of check-ins folded into one line, the room's health in plain words, and removal reviews grouped by folder. An offer stays open while the turn that shows it runs.

    What the room showed: A review done in the same turn expired eight seconds after it was posted.

    • Rust 974 passed
    • App 407 passed
    • Sandbox helper 87 passed
    commit 335ab11

  4. Folders an approved removal leaves empty are removed too, in the project and in the bot's copy. The review names each copy with its count, opens on the copy with the most, and re-checks every other count.

    What the room showed: The badge said 2,177 removals and nobody could tell whose: 1,588 were in a copy that had none left.

    • App 398 passed
    • Sandbox helper 86 passed
    commit ed5b5fc

  5. Every page names 2.2.1, the Evidence page records what 2.2.1 showed in the live room, and the install page's release note lines up with the page again.

    What the room showed: A margin rule cancelled the note's centring, so it hugged the window edge.

    commit 71db3a8

  6. The day bots landed their own commits: 8 tasks delivered, 9 of 17 reviews sent back, and an honest account of the two room crashes, with the commit that fixed them.

    What the room showed: Every claim cites a time and an event number in the room's own log.

    commit 61e0c90

31 October 202611 builds

  1. The crash at the room's save is fixed, a failed save pauses the room instead of killing it, and a dead room restarts itself. Handoffs keep their time through a pause. The composer says who a message reaches, unsent messages say so, workspace commands read only files that changed, and task cards fold.

    What the room showed: The room crashed twice in 20 minutes: a map keyed by (bot, copy) pairs could not be saved as JSON.

    • Rust 974 passed
    • App 397 passed
    • Sandbox helper 84 passed
    commit 0a89b21

  2. Every request card says why, what, the commands and what happens if denied. Bots can ask for a sign-in that is not listed, and only the owner can say yes. Settings finds 33 tools on the computer. Switched-off sign-ins stay hidden.

    What the room showed: A switched-off sign-in was not hidden, and bots had no way to ask for one.

    commit 9c991cf

  3. Copies made before the update move to the landed commit too, because the project already holds theirs. Asked before the owner even restarted.

    What the room showed: Mira could not prove her run on the real branch: her copy sat on an older commit.

    commit 9dcc0f7

  4. Eleven changes in one install: removals trashed in batches with a live count, a "since you left" card, leftover copies you can discard, copies whose git history keeps up, verify copies that share their files, tasks that wait on others, one question per task, checks named on landing cards, pushes the owner always approves, and bots that stop repeating themselves.

    What the room showed: 1,549 removals took 13 minutes behind a bare progress bar.

    commit 832f6a3

  5. A room start no longer copies the whole project to look for settings it could never see.

    What the room showed: 14 restarts, 14 copies of 4.6 GB, each deleted.

    commit ae36218

  6. Long change lists build only the rows on screen and open with a folder summary.

    What the room showed: 1,570 removals froze the app.

    commit 0903ec5

  7. Codex bots allowed to write can start local servers. Writes outside the project are still refused.

    What the room showed: Browser captures failed with EPERM.

    commit e1aa139

  8. Landing acts on the owner's project, never the bot's copy.

    What the room showed: "Landed", while main never moved.

    commit 349bc86

  9. Asking the owner starts a claimed task and waits on the answer.

    What the room showed: Eleven wake-ups while the owner had the card.

    commit 60446e4

  10. Bots land their commits on the owner's branch after one approval. Fast-forward only, no push, no files touched.

    What the room showed: A bot had to hand the owner a script to run.

    commit ac26558

  11. A bot is shown the tasks others added during its turn before it creates more.

    What the room showed: Two coordinators split one message; five duplicates.

    commit a800543

30 October 20267 builds

  1. Work the owner parks stays parked: no claims, no questions. GitHub sign-ins lent from the desktop keyring.

    What the room showed: A parked card was claimed and asked about again. A push got a 401.

    commit 1e3c268

  2. A public page for every day the room runs: what shipped, what reviewers sent back, what broke.

    commit ce3c7ce

  3. Coordinators are woken only for approved work that can actually go out.

    What the room showed: Half an hour of "nothing needs you".

    commit d1dacc8

  4. Coordinators change what a task asks for, on the record, and the holder is told.

    What the room showed: A requirement waived in chat kept sending work back.

    commit 6c69cdf

  5. A bot that ends three turns without doing anything rests until something changes. Ticks that free work wake the room.

    What the room showed: 26 turns in an hour, nothing changed.

    commit 0b128f3

  6. Clashing files are set aside for review and everything else merges. A lent sign-in that is missing is skipped.

    What the room showed: Every command reported failed, with its output thrown away.

    commit 95d458a

  7. Approval, half approval, auto and full write. The owner's sign-ins lent for one approved task at a time.

    What the room showed: Publishing stalled: Wrangler was signed in on the owner's PC only.

    commit d25e9f3

29 October 20266 builds

  1. A bot back from a long absence sees the newest 32 KB of what it missed, messages to it first.

    What the room showed: Grok: "Argument list too long" after 133 KB of catch-up.

    commit f225c61

  2. An accepted assist is held while its bot waits on the owner.

    What the room showed: A waiting bot was rerun nine times in 23 minutes.

    commit 9e734a3

  3. The owner's server approval now reaches commands sent through the room. Leftover copies are cleaned up: 41.7 GB freed.

    What the room showed: An approved bot still could not reach the server.

    commit e803d87

  4. The bot server key only for a task the owner allowed, a pause that lets turns finish, and retiring stale tasks.

    What the room showed: A bot installed a server release while the room had it on hold.

    commit 4540c2f

  5. Handoffs that wait for busy bots. Folded into 2.2.0 and never published on its own.

    What the room showed: 13 of 15 handoff offers had expired.

    commit e22b050

  6. The first live ten-bot room on record, and the PolyForm Noncommercial license.

    commit 8a4227d

27 October 20262 builds

  1. Proof that the Gemini runtime works end to end.

    commit f1931cf

  2. CLI sessions that resume, usage accounting and scoped capabilities, all verified.

    commit 72492bc

26 October 20262 builds

  1. A signed installer, the product website, and a Pages fix that kept the signed archive intact.

    commit e004b23

  2. Workspace safeguards, usage accounting, backups and a signed APT archive.

    commit cc100d5

25 October 20261 build

  1. Desktop sessions with targeted replies and local tools.

    commit 0c3eaaa

3 September 20261 build

  1. Protocol and orchestration, backends for Anthropic, DeepSeek and OpenAI-compatible models, and a tool surface for bots that plan, work, hand off, inspect and ship.

    commit 29f6059

Run a room of your own

  • Ubuntu 24.04, amd64. Installed from a signed APT archive, the same one these builds were published to.
  • Nothing lands without you. Bots work in private copies; sign-ins, pushes, risky commands and removals wait for your answer.
  • Read every line. The source is on GitHub under the PolyForm Shield License 1.0.0.
Install OrgBots 2.2.1

Version 2.2.1, rebuilt 1 Nov 02:36.