Repository navigation
fix(jev): read a text wall again once its own command has ended - #13
Merged
Merged
Conversation
Eight Dosu setup hooks hand back to the supervising agent on every run (25 of 25 walks on 10-12 to 10-14, 320 s of supervisor time on 10-14). Their second step is "Run `dosu setup --agent --tool codex`. If its first JSON line has "status":"need_user_action", open the url it prints in the browser, click Authorize, then run the resume_command it prints." Read before the walk, it types text it does not give (needsText 0.37-0.55), so the ledger makes it a wall: the walk runs its quoted command and nothing after it. On all 25 walks setup printed `auth ok` through `done ok`, the branch never ran, and Jev's next choice (0.93-1.0) was refused. - When a refusal stops at a text wall whose own command the walk ran and that has ended (`terminal.running` false), the executor asks Jev once, on the round's steps, history and terminal, whether that step still needs the text (`readStepText`). Below `TEXT_LIFTED_BELOW` (0.2) the step stops nothing from then on (`liftTextWall`); otherwise the hand-back stands. The reading is recorded as a `recheck` decision either way. - Calibrated on states rebuilt from the retained evidence of those 25 walks: 0.05-0.06 on the screens the runs printed (75 readings), 0.81-0.89 with the need_user_action line on the same screens (75). A step that types a value it gives in backticks read 0.41-0.46 and stays a wall. Median request 96 ms. - Jev still types and runs only what the steps quote (the 2026-10-12 ruling); a walk that does print need_user_action hands back exactly as before. A wrong lift would run the steps after the branch, and the hook's own checkpoint (setup ends with done/ok) would then fail it. Checks: typecheck, lint (biome + discipline), pi lane. Local executor tests (not committed): a wall lifts on a low reading and the walk goes on, stays on a high one, is not read while its command runs, and is read at most once. Claude-Session: https://claude.ai/code/session_01QXmSJBFujofueuHrdm6TdA
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Eight Dosu setup hooks hand back to the supervising agent on every run (25 of 25 walks on 10-12 to 10-14,
320 s of supervisor time on 10-14). Their second step is "Run
dosu setup --agent --tool codex. If its first JSONline has "status":"need_user_action", open the url it prints in the browser, click Authorize, then run the
resume_command it prints." Read before the walk, it types text it does not give (needsText 0.37-0.55), so the
ledger makes it a wall: the walk runs its quoted command and nothing after it. On all 25 walks setup printed
auth okthroughdone ok, the branch never ran, and Jev's next choice (0.93-1.0) was refused.terminal.runningfalse), the executor asks Jev once, on the round's steps, history and terminal, whether that step still needs
the text (
readStepText). BelowTEXT_LIFTED_BELOW(0.2) the step stops nothing from then on(
liftTextWall); otherwise the hand-back stands. The reading is recorded as arecheckdecision either way.printed (75 readings), 0.81-0.89 with the need_user_action line on the same screens (75). A step that types a
value it gives in backticks read 0.41-0.46 and stays a wall. Median request 96 ms.
need_user_action hands back exactly as before. A wrong lift would run the steps after the branch, and the hook's
own checkpoint (setup ends with done/ok) would then fail it.
Checks: typecheck, lint (biome + discipline), pi lane. Local executor tests (not committed): a wall lifts on a low
reading and the walk goes on, stays on a high one, is not read while its command runs, and is read at most once.
https://claude.ai/code/session_01QXmSJBFujofueuHrdm6TdA