The Cyborg Workflow.
One terminal writes the code. Another terminal configures the APIs. Two Claudes in parallel changes what one person can build in an evening.
For a long time, the bottleneck on solo building wasn't writing code. It was the seams. Wiring up Stripe webhooks. Configuring Venmo. Reading docs for Twilio. Setting up Vercel. Each one a thirty-minute context-switch from whatever you were actually trying to ship.
The setup I run now collapses that. It's not a tool. It's a posture.
Two Terminals, Two Claudes.
On my left, Claude Code1 in a terminal, working on the Next.js app — writing the booking flow, the credit logic, the API routes. On my right, Claude in a Chrome extension2, configuring the Venmo developer console and the Twilio dashboard and the Vercel environment variables. Both running at the same time. Both doing real work.
Claude on the left writes the webhook handler. Claude on the right registers the webhook URL with the third party. Claude on the left writes a feature flag. Claude on the right toggles it in the dashboard. The handoff happens in seconds, by me, just by looking from one terminal to the other.
That's the actual experience. Not faster typing. Not better autocomplete. Two simultaneous threads of work that I'm orchestrating, not executing.
The Bottleneck Isn't Code.
Anyone who's shipped a real consumer-facing app knows the math: writing the application logic is maybe a third of the work. Another third is wiring it to third-party services. The last third is the operational tail3 — environment configuration, dashboards, dashboards-of-dashboards, cron settings, webhook secrets, API keys.
AI got really good at the first third in 2024. Most people I talk to about Claude Code are still asking it to do only the first third — they fall back to manual work for the wiring and the operations. Which means they're still bottlenecked on the same two-thirds of the work as before.
The cyborg workflow is the realization that browser-using AI extends the productive surface to the operational tail. The dashboards are just web UIs. A model that can navigate a webpage can configure Twilio. The fact that nobody's officially "supposed" to use a browser-using assistant for this is irrelevant — once you've felt the speed difference, going back is unthinkable.
Two Becomes Thirty.
What I started with was two terminals. What I ended up with, six months later, was a fleet — sometimes thirty parallel Claude Code sessions running across multiple repos. The cyborg workflow scales linearly until it doesn't, and the place where it breaks is coordination.
Five sessions all want to commit to the same main branch. Two sessions both touched the same file. One session needs to know what another session learned three days ago, and grepping ~/.claude/projects/*.jsonl takes too long to maintain flow.
That's the problem CCC4 solves. It started as a kanban for tracking which Claude is doing what, and it grew the two pieces I needed once the fleet got real: a markdown-based commit-coordination protocol so sessions stop racing each other into the git index, and a local search index over every transcript so I can ask "what did I decide about that thing two weeks ago?" and get an answer in milliseconds. Long-form on those two fixes here.
One Person Is Now A Small Team.
The cyborg workflow isn't a productivity hack. It's a structural shift in what a single experienced operator can ship. The Pilates studio platform — three weekends. The expense tracker — a long weekend. The marketing analyzer — an afternoon. None of these would have been weekend-builds five years ago. None of them would even have been three-month-builds for a non-engineer.
That changes the cast of who can build software for what. It pulls the threshold for "worth building" down by an order of magnitude. The implications for small businesses, in particular, are the thing I'm spending most of my time on now — long-form here.
The short version: if your job is to build, and you're still doing one thing at a time, you're leaving most of the leverage on the table.
Try CCC.
Watch the 2:46 demo on YouTube →
The fleet-scale tooling I use, open-source. Two-line install on macOS:
git clone https://github.com/amirfish1/claude-command-center cd claude-command-center && ./run.sh
Three doors
If this resonated, the most useful next step is one of these:
More Field Notes → Email me → Star CCC →