I try to break Empryo before you do
Agents hunt for bugs in Empryo every day. A second model has to reproduce each report before it counts, every fix ships a lint rule so the same bug cannot come back, and 405 automated checks run against the real build.
In numbers
- bugs found
- 2491
- 437 more thrown out on review
- fixed
- 1622
- 1 waiting for a fix
- guarded by a lint rule
- 1229
- so they cannot come back
- automated checks
- 405
- 298 on macOS, Linux and Windows
The bug machine
A bug is one file, and the folder it sits in is its state. Each agent does one job, writes its part and moves the file on. Nothing moves without proof.
Hunt
Hunters read one slice of the code for one kind of bug. A report counts only when they reproduced it in a throwaway home folder.
Review
A reviewer on a different model runs the reproduction again, then approves the report or throws it out.
Fix
A fixer removes the root cause in the terminal app, the desktop app and headless mode, and proves it before and after.
Check the fix
A fix reviewer reruns the proof. It is pass or fail, and a pass with a minor issue is a fail.
Land and guard
The fix lands as one commit, with a lint rule that fails whenever someone writes the same mistake again.
- Fixed, and a lint rule guards it1229
- Fixed393
- The fix passed its review0
- Approved, waiting for a fix1
- Waiting for review868
437 more reports were thrown out on review: a second model could not reproduce them, or the behaviour was intended.
Every fix ships a guard
A fix without its guard is not done. The next agent that writes the same mistake fails the lint before anyone sees it.
2340lint rules, written with the fixes
A rule ships with its fix. It has to flag an example of the bug, pass the fixed version, and find the same mistake nowhere else in the code.
1,887risky patterns counted, and the count only goes down
Swallowed errors, empty catch blocks, waits on the clock and unsafe casts are counted across the code and committed as a floor. Raising it takes a diff with a name on it.
One run, replayed
The machine finds new bugs, and the checks keep the old ones fixed. This is a real slice of them, played back from its report.
0of 26 done
September 23, 2026, Empryo 3.8.6-beta, build df8921843
- macOS0 of 13
- Read only tool in a read only modequeued
- A saved session records the mode it ran inqueued
- An unapplied mode never runs at full powerqueued
- An unapproved plan does not unlock a restricted beltqueued
- Architect reads but never writesqueued
- Auto approves what default refusesqueued
- Denied edits are not reported as editsqueued
- Mode banner reaches the modelqueued
- Plan mode keeps the approval gatesqueued
- Plan mode never approves its own planqueued
- Restricted modes deny every mutating toolqueued
- Switching mode mid session takes effectqueued
- Tool schema is stable across modesqueued
- Linux0 of 13
- Read only tool in a read only modequeued
- A saved session records the mode it ran inqueued
- An unapplied mode never runs at full powerqueued
- An unapproved plan does not unlock a restricted beltqueued
- Architect reads but never writesqueued
- Auto approves what default refusesqueued
- Denied edits are not reported as editsqueued
- Mode banner reaches the modelqueued
- Plan mode keeps the approval gatesqueued
- Plan mode never approves its own planqueued
- Restricted modes deny every mutating toolqueued
- Switching mode mid session takes effectqueued
- Tool schema is stable across modesqueued
- Windowsnot in this run
0 of 26 doneTwo real reports from the same slice, 13 checks on the modes area run on macOS and then on Linux. Windows was not part of this slice.
Where it runs
macOS
- headless276 checks
- terminal91 checks
- desktop64 checks
Linux
- headless278 checks
- terminal89 checks
- desktop22 checks, start-up only
Windows
- headless242 checks
- terminal74 checks
- desktop30 checks
On Linux and Windows the checks use the release archive you download. A filled dot means the checks really drive that form of the app; a half dot means they only confirm that it starts.