The story isn't the tech
Phase 2 of Berceuse just closed. Qwen Code CLI ships on node 3 via a paperclip adapter I cherry-picked from an unmerged upstream PR this afternoon. That's not the story. The story is the mental-model shift.
Paperclip compresses what a 200-person org usually burns an ERP budget on — role hierarchies, task decomposition, review gates, dependency resolution, approvals — into a SQLite file and a skill document. One event loop plus a protocol-documented agent library. That's it. That's the whole thing.
A month ago I thought the shift I was seeing was Notion-vs-Evernote scale. Maybe Google-Docs-vs-Office. I was wrong. This is the first time in 30 years of software a single person can run an actual org chart made of software, for personal use, at a homelab's cost of electricity.
The fleet
- node 1 — dual 3090 Ti, Qwen3-Coder-Next inference (Berceuse's current coder)
- node 2 — 3090, media generation
- node 3 — CPU/RAM master, runs Berceuse itself
- node 4 — dual 3090, LoRA fine-tuning + classification
- node 5 — ~2 weeks out, dual 3090 with TP=2. Not frontier. Close enough.
And the first tool my agents are going to build isn't for a client, isn't for a product, isn't for anyone's OKRs. It's a Gmail fetcher. For my own inbox.
A CTO agent will receive a "triage my mail" PRD, split it into sub-tasks for a news watcher, a subscription killer, a signal aggregator. A reviewer agent will check the diff before merge. A paperclip routine will wake the whole chain every 10 minutes. I will be the only human in the building.
Why troubled-excited
Not because the tech is new — tech is always new. Because the economics that used to gate this are gone.
You used to need a company to have a company. You don't anymore.
The quiet sci-fi moment
The weird thing is how quiet it is. No announcement, no keynote, no Verge article, no HN thread exploding.
It's 11pm on a Tuesday and I'm committing a cdk8s chart that references a custom image that references a cherry-pick branch that references a PR that references a repo that's only 6 weeks old, and in two weeks node 5 boots up and I'll tell the CTO agent to build something, and it will.
Sci-fi didn't arrive in a product launch. It arrived in a local branch on a Tuesday night, in a homelab nobody else has heard of. And the first thing it's going to do is read my email.
The first brick
The Gmail fetcher is small on purpose. M1 isn't the full agent chain — that's M3 territory. M1 is the tool. One coder agent, one fresh repo, one real deliverable: a standalone Python thing that fetches emails since a cursor and produces structured output. A human reviews, a human merges, and the first value is in the bank.
But once the tool exists, the chain becomes real. A triage agent reads the output. A classifier fans it out. A subscription killer unsubs, a news watcher aggregates signal. The tool becomes the interface between the physical world (my inbox) and the agent company (Berceuse's Personal workspace).
Every tool Berceuse builds is a new interface between the physical world and the agents. Gmail today. Calendar tomorrow. Banking. Home automation. Reveille. Fine-tune workflows. Media pipelines. Every domain gets a tool, every tool gets consumers, every consumer is an agent, every agent reports to someone.
I used to think of software as a thing I build for users. Now I'm building software for software I also built, and the users are software too, and the only user left on the human side of the loop is me.
Troubled-excited. Mostly excited. A bit dizzy. Laying the first small brick of what's going to be many chapters.