“participants using ParallelPilot increased ticket throughput by 63% in short coding tasks and supervised an average of one more concurrent agent at peak, while their tracking effort and context switching dropped. [...] These gains were not accompanied by significant improvements in perceived control or perceived success in redirecting the agents.”

Rare empirical, human-subjects evidence on supervising concurrency. Formative study (N=14): typical setup is 3 concurrent sessions (max 3-8), parallel use accounts for 45.3% of AI coding, triggered by idle time waiting on builds/tests; all 14 reported a coordination and monitoring tax ('over your brain, fried quickly'; 'like a quarterback across three sessions'). They name five supervisory practices, PILOT: Plan, Isolate, Log, Observe, Triage. The authors' own Discussion flags an 'abstraction tension': status awareness 'did not by itself establish whether its code was correct', so tools should lower the cost of the re-engagement moment (one-click return to the CLI, lead-in messages, retrievable history). Limitation: short coding tasks, design probe not a production tool. Strong anchor source for a note on the human attention ceiling; pairs with Abralo (3-4 agents) and Delegator (review WIP limit).