As of July 2026, the loudest signal on Hacker News this week wasn't a new model — it was an engineer admitting that running 4-5 parallel Claude Code agents on an 8GB MacBook Air pushes up to 90 commits a day, and that the machine can't survive it without help. Every agent building, testing, and running a dev server at once is "the fast lane to a force quit and restart." So the fix wasn't a bigger laptop — it was software: a local merge queue that lands one commit at a time, fully tested, before the next agent gets a turn.
A second post from the same 48 hours makes the harder point: git worktrees are not an isolation boundary for coding agents. Worktrees share the same .git directory, the same object store, the same refs. Two agents working in separate worktrees can still step on each other — a checkout in one silently moves a branch pointer the other agent is relying on. It looks like isolation. It isn't.
The pattern: parallelism is free, coordination isn't
Put these two items together and you get a clean lesson for anyone running an AI agent stack, not just AI-assisted coders. Spinning up more agents is trivial — add a prompt, add a process. What's expensive is everything downstream of that: making sure two agents don't corrupt shared state, making sure output lands in order, making sure a crash in agent three doesn't take down agents one, two, and four. The HN engineer had to build a merge queue by hand because nothing shipped with one. That's a real, uncounted engineering cost sitting underneath a tool that markets itself as "just describe what you want."
This is the same shape of problem we flagged in our breakdown of what actually runs under the hood of an agent stack: the visible cost is the subscription or the API bill. The invisible cost is the queueing, the isolation, the monitoring that keeps five things running at once from becoming one thing on fire. Nobody puts "merge queue" or "isolation boundary" on a pricing page, and almost nobody budgets for it until the laptop crashes at commit 63.
Why this matters if you're not writing code
Swap "coding agents" for the agent stack a local business actually runs — a visibility module checking how ChatGPT and Perplexity describe you, a content agent drafting posts, a booking agent texting back leads, an outreach agent working a list, a voice agent answering the phone. Run those in parallel without real coordination and you get the SMB version of the same failure: the booking agent double-books a slot the voice agent just filled, the outreach agent emails a lead the CRM agent already flagged as closed, two agents write conflicting notes to the same customer record. The failure mode isn't a crashed MacBook. It's a client getting two different answers from two different agents in the same afternoon.
That's the real argument in the build-vs-hire decision. Anyone can wire up five agents against an API in a weekend. Keeping those five agents from stepping on each other — the merge queue, the isolation, the ordering guarantees — is a second, harder project that most business owners never intend to sign up for. The HN post proves the point from the other direction: a solo engineer with deep infrastructure skill still had to build custom tooling just to keep 4-5 agents from wrecking his own machine. Scale that coordination problem to a live customer-facing stack and the stakes go from "force quit and restart" to "a customer's booking got overwritten."
What to check this week
If you're already running more than one AI agent against your business — even something as simple as a chatbot plus an email drafter plus a review responder — ask three questions before adding a fourth:
- What happens when two agents try to write to the same record at the same time?
- Is there an actual queue, or are you trusting that timing will usually work out?
- If one agent fails mid-task, does it take the others down with it, or does it fail alone?
If you can't answer those in one sentence each, you don't have an agent stack yet — you have several agents that happen to run near each other.
What this means if you're weighing AI marketing or an agent build: the coordination layer — not the AI model — is where DIY agent projects quietly fail, and it's exactly the layer most vendors don't mention until something breaks.
Want to see where your business actually stands before you build or buy anything? Start with the free AI Visibility Report.