An agent's status question stops an auto-approved run for a person #280
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happens
Run 134 (vLLM, auto-approve on) stopped at "Needs you" in the judge. While its
browsersubagent ran in the background, the judge called thequestiontool as a "status checkpoint": "The file:// browser check is still running in the background… No action needed." Its one option was "Continue when ready". Braid opened it as a gate withexpire_action: holdand no expiry, so the run waits for a person indefinitely. Auto-approve doesn't cover agent questions.Fix
question.Done when
An auto-approved run whose agent asks a one-option or defaulted question carries on without a person.
From #279, run 134.
It loops. Run 134's judge asked four of these in about four minutes ("Judge progress", "Waiting on browser run", "Awaiting browser report", "Still awaiting report"), each with one option, "Continue when ready". Each answer woke it; with its browser subagent still running it had nothing to do, so it asked again.
So answering automatically isn't enough on its own: it would only make the loop faster. Better:
questionwith: "end your turn; the subagent's report wakes you".Shipped in #284 (the backend-comparison fixes), confirmed on production in run 139 (cmoriarty/breakout-planned, vLLM, auto-approve on).
Run 139's judge sent its
browsersubagent 12 tasks over 29 minutes: a desktop and a phone playtest throughwindow.__app, with screenshots and console reads. It called noquestiontool, and the run opened no gate: the judge waited for each report by ending its turn, and the auto-approved run never stopped for a person. Round 1 passed.