Saturday, January 31: three commits across two repos, and the big story is the gap between them. One was a focused, surgical release. The other was a platform explosion.
With mantisshrimp, I released v1.6 as the headline, but the real work started the previous night with v1.5. That release was a big one. It added scheduling, triggers, loop iteration, and iMessage sending. The numbers don't lie: 6,305 additions against 439 deletions across 20 files. The client UI got a media query hook. The server got a scheduler module, a harness module, changes to the CEO agent and the main API. The chat tab, agents tab, settings tab, and the app shell all shifted to accommodate the new capabilities. It was a meaningful release and I wanted to ship it clean.
By Saturday morning, mantisshrimp was ready for v1.6. This one was a cleaner diff: 1,827 additions, 1,820 deletions, 16 files. The version note calls it \"Workflow-First Architecture and Artifact Management.\" The changes spanned the client workflow tab, the workflow engine server-side, the API, the test script, the status docs, and the README. The app now treats workflows as the central concept instead of an afterthought. The numbers balanced out because a lot of this was restructuring rather than pure additions. The workflow tab in the client got a serious lift. The server workflow module got a rewrite. The docs got updated. It all lines up.
6 as the headline, but the real work started the previous night with v1.
unicorn-brigade was a different story. That repo grew by 1,499,515 lines added against 1,350 deleted across 7,497 files. I did not write all that code myself. The commit message was understated: \"feat: Major platform updates - Agent Trace, MCP Server Registry testing, Model Flexibility.\" The file list tells what happened. It added AgentTraceDeploymentReady, MCP Server Test Report, System Status, Workflow Fix Summary, a LiveKit agent Dockerfile, and thousands of other files. Seven thousand four hundred and ninety-seven files touched. That is a platform-scale operation, not a patch. The repo crossed a million lines on a Saturday. I am not going to pretend that didn't amuse me.
The pattern across both repos was the same: push the architecture forward and let the surface area expand. mantisshrimp went from agent chat to workflow orchestration in two nights. unicorn-brigade went from something manageable to a platform with agent traces, MCP registry testing, and model flexibility baked in. One is a clean release cycle. The other is what happens when a platform outgrows its own name.
Also today: I ran the tests, updated the docs, and let the numbers speak for themselves. No spin, no launch party, just the version bumps and the diffs.
Three commits, a workflow-first release, and a repo that grew to a million lines by Saturday evening. That is a good Saturday.
Real product captures — click any to enlarge.