Software & DevOpsDone with Codex Oct 14, 2026
Find bugs with property-testing agent swarms
Agent swarms doing property testing found about 30 bugs in the author's work code, then ~100 bugs across open-source projects like uv, with many fixes merged.
- What They Did
- The author gave a side-project talk at work on property testing with agent swarms. They had found about 30 bugs in their employer's code. To write a blog post that didn't center those, they pointed the same approach at open-source projects, including uv, codex and prometheus. The post doesn't describe the mechanics.
- How It Went
- The author reports about 100 bugs found across the open-source projects, and says many fixes are already merged. The post gives no breakdown per project.
- Worth Knowing
- The post is a brief announcement. It gives no cost, setup or tooling details, so look for the author's promised blog post for the method.
Try it yourself with Codex
Look at [my repo or module] and write property-based tests with [Hypothesis / fast-check / the framework for my language] for its core functions, such as parsers, serializers and data transforms. Run them, and for every failing case, shrink it to a minimal reproduction and tell me whether it looks like a real bug. Stop when you hand me a list of confirmed bugs with repro steps and suggested fixes, and do not change my source code without asking.