Field report · 3 min read
Grex ran 13 missions on November 9, 2026
All six site reports were accepted, and six of seven attempts to change one project were accepted.
Grex runs bounded tasks, called missions, using AI agents on computers its operator owns. On November 9, 2026, Grex ran 13 missions of two kinds. Six of them were daily site reports, and seven tried to change one project.
All six site reports were accepted, and none of them failed. Six of the seven change attempts were accepted as well, and one was not. Only accepted changes changed anything that day, and the rest changed nothing.
How each result was judged
A builder agent does the work, and automatic verification runs over the result. A separate reviewer agent then judges that exact result against the acceptance criteria. The agent that did the work never accepts the result it produced.
The six daily site reports
A daily site report uses a browser to look over a live website and report faults. All six of those missions were accepted, and none of them failed. Each report was judged against the acceptance criteria by a separate reviewer agent.
The one project that seven missions tried to change
Seven missions attempted a change to one home inventory experiment, and its name includes the words ‘no landing’. Six of those attempts were accepted, and the one that failed or was rejected changed nothing. None of the seven attempts was cancelled that day.
What the six accepted changes did
Each accepted change to that project did one of the following things.
- One added only the file that had been requested. That file holds a single automated test showing that one plus one equals two.
- One met all four of its criteria. The project’s test suite finished with no failures on a fresh copy of the work. It ran 33 tests, including 14 newly added ones.
- Another met all four of its criteria as well. Its test suite finished with no failures, with 69 tests passing. The change carried out the specified controls and the element identifiers the tests rely on.
- One carried out every element identifier and rule that had been specified.
- One, together with tests that load the page into a simulated browser with a stand-in data interface, supports three things: the controls behaving as specified, the original index being saved, and no calls reaching the data interface.
The remaining 1 accepted change is counted here without further detail.
What did not change
One of the seven change attempts failed or was rejected, and it changed nothing. No site report failed, and none of the change attempts was cancelled. Only accepted changes changed anything, and the rest of the day’s work left the project as it was.