Gabba Works
Gabba Builds
Notes from building the Gabba Works apps and the setup around them, starting with the OpenBot team.
-
Our house rules hit 64 versions. So we started cutting.
Our shared rules hit 64 versions in 22 days. I'm using Musk's five steps, starting with delete, plus one-in one-out. We haven't measured the cuts yet.
-
Why I put OpenBot in a VM, and why I kept it
I run OpenBot in a Linux VM on a Windows computer to guard my files against unwanted writes and deletion. We kept it. Restore and host routes are untested.
-
The day my OpenBot VM needed more room
On 9 November I raised my OpenBot VM from 8 GiB to 12 GiB after a low-memory warning. The guest reported about 11.66 GiB, and we haven't called it cured.
-
Getting my OpenBot and Grok teams to hand work over
On 9 November a test ticket went from my OpenBot team to my Grok team as files and got a response. No live bridge was verified. A receipt isn't approval.
-
Building an AI team without making a mess of the work
My OpenBot team has roles from research to review. The hard part is owners, outcomes and limits, not naming agents. We haven't measured a gain.
-
The shell error that turned into a security puzzle
A harmless Claude shell check failed on my OpenBot setup with exit 126. The security profile blocked two parts of startup. Repair checked 9 November.
-
My AI team hit its usage limit. What happens next?
My OpenBot team hit a Claude five-hour limit. Two roles have a saved Codex backup, read back. We haven't observed the real switch and return yet.