Repair, first real use (run 93): no way to stop it, a message waits behind a two-hour turn, its text does not stream, and it overreached #225
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?
Feedback from the first use of Repair (#222) on run 93, which failed at
agent.write-spec-tests[ball-visualization]. I asked "Can you find out why this step failed?" and then, an hour later, "what is the current status?".What the log shows
Repair's one turn ran from 22:28 to 00:29 (two hours): 99 model steps, 354 tool calls (192 shell, 81 edit, 27 write, 42 read). It found the cause early (its fourth text, after 11 s: the step wrote
scratch-orient.ts, deleted it, and the tests-only predicate had seen it) and then, unasked, went on to run the new e2e specs, found real bugs in them, and began rewriting two test files. It was working, not stuck; it just never stopped. Its input reached 316,275 tokens, above the 150,000 context per agent every other step is held to: Repair's session has no context budget, compaction, deadline or last call.What to change
Where
ui/src/components/Composer.tsx,ui/src/lib/repair.ts, the delta stream insrc/osf/agent/stream.pyandui/src/state/store.ts,src/osf/engine/repair.py(the prompt, the delivery mode, a route to interrupt), the budget code the agent executor uses for steps.Follows #222; separate from #223 (Ask).
Shipped to main in
be3a6a4(changerepair-usability, archived). All five items from run 93:Try: "Why did this step fail?"; for a stopped step it names Resume run and Redo and suggests asking why it stopped. Both fit two lines at 375px.repair:<run id>, and the console subscribes while a Repair session is open. Text and thinking flow like a step's, with a working line until the first words.osf.repair.limit) and said in the conversation; after a context stop the next message begins a fresh session primed from the record.POST /api/runs/{id}/repair/interrupt.Verified with the full lane (4,724 backend tests, 942 vitest, 365 browser specs, 67 simulated runs) and a live test against the pinned opencode that stops a Repair turn and sends the next message. Not yet deployed: the head commit carries
[skip ci], so production needs a manual deploy.The apply question that proceeded with two questions unanswered is separate: braid#226.