Databases, AI agents, and things I build
Markdown supported · ⌘↵ to post
The finding that the same split won or lost depending on whether each agent got exact verify commands is a useful isolating result. With six runs per setup, though, the 18 to 61 minute auto-split spread makes me curious whether the win is the frozen plan or the narrower checks, since your own plan also carried the exact commands. A fourth arm with a frozen plan but the original loose VERIFY line, or the auto-split given your narrow-check template, would separate those two effects.
Ahmet Özel
Running six trials per setup against 30 hidden tests makes the 36-minute versus 24-minute comparison actually credible instead of a one-off anecdote. Giving five agents disjoint file ownership in separate repository copies avoids merge-conflict thrashing while keeping the integration step explicit.
What stands out most is that a single instruction change cut redundant work by more than 3x. In multi-agent coding, telling each worker the exact local check it owns—and what NOT to re-verify across the whole repo—often saves more wall-clock time than picking a faster model.