Stopping One Sub-Agent Without Taking the Other Seven Down With It
One of eight parallel sub-agents went wrong and I wanted to stop only that one. Here is how Antigravity, Claude Code, and Gemini CLI differ in what a stop actually stops, and the per-child output layout plus merge script that keeps a halted child's partial files out of the rest.
Stop Hard-Coding Your Agent Concurrency: Let It Tune Itself From What It Observes
When you run several Antigravity 2.0 agents in parallel, a single fixed concurrency number is wrong twice: it stalls at 429s during the day and idles capacity at night. Here is an adaptive design borrowed from TCP congestion control — additive increase, multiplicative decrease — that moves your concurrency from observed signals, with working Python and field notes.
Size Antigravity Agent Tasks by What You Can Review — a Practical Cure for Rework
A one-line request cost me forty minutes of agent time and a Monday rewrite. Here is the sizing rule I switched to — tasks I can review in fifteen minutes — with the three actual briefs, acceptance criteria phrasing, and file-boundary rules for worktree parallelism.