Image: dev.to
Six parallel agents froze a production server
Claude Code ran six agents at once on the machine that served the developer's site; together they ran it out of memory and froze it.
Credits
- Article author alex_iolan Source ↗
Earliest dated source:
Don't run several agents on the machine that serves your site. Builds and tests eat memory; do the work elsewhere and deploy the result.
The full story
Given a list of six tasks, Claude Code started six agents in parallel, each installing dependencies, type-checking, testing and building, on the same server that hosts the developer's site. The server had 10 GB of RAM with about 7 free; six builds needed 9 to 18 GB.
Linux didn't kill anything. The machine started swapping to disk, spent all its time doing that, and hung. Site, admin panel and publishing queue were frozen for 17 minutes until a hard reboot. Each agent did its job correctly; nobody, human or model, had added up the memory.
How it was done
Tools
Themes
Loading themes…
Sources
From the maker's own write-up or code. We summarise what they report; we haven't tested it ourselves.
- DEV: Six AI agents froze my production server. Each one did the right thingArticle author: alex_iolanPublished
The developer's write-up, with the rules they use now.