MENLO PARK, Calif. — Coding assistants have become good at producing code that looks right. The harder question for the developer who has to merge it is whether anyone checked. Remy, the coding agent from Corepass, answers with what amounts to an evidence trail: a record of the checks it ran, what it changed when one failed and an explicit account of what it did not verify.
The behavior, set out on Remy’s product page, follows a fixed order. After changing code, Remy runs the relevant tests, type checks or build. If something fails, it looks for the cause, fixes it and reruns the same check — not a different, easier one. The product page puts the last step plainly: “Then it tells you what ran, how it went, and what it didn’t verify.”
- Run checksTests, type checks or the build
- Find the causeWhen a check fails
- Fix and rerunThe same check, run again
- Report backWhat ran, how it went, what wasn’t verified
The check that failed is the one that runs again
Why the same check matters
The insistence on rerunning the identical check is the point. A fix followed by a different test, or by no test at all, leaves open whether the original failure is gone. Rerunning the check that failed ties the fix to the evidence that it worked, and puts that evidence where the reviewer can see it.
“Then it tells you what ran, how it went, and what it didn’t verify.”
Saying what wasn’t checked
The last part of the report may be the least common among coding tools. Remy’s closing note separates what was verified from what was not; in the product’s own demonstration, a task ends with two lists, one headed “Verified” and the other “Not verified.” A change to code that no test covers, for instance, would be named as unverified rather than passed over.
Review before the merge
Verification is one layer. Remy’s documentation describes a separate code review mode that reports findings by severity, each with its location, its impact and the evidence behind it. In the workflow on the product page, a review bot, Bugbot, reads the diff and looks for what the tests missed before the pull request goes out.
Corepass lists “Keep work reviewable” among the principles it builds by, and the verification report is the clearest expression of it in the product: the agent does the checking, and the developer gets the record needed to decide whether to merge.