When an agent stage stops at its step budget (e.g. 60/60), the run parks and the work it did is kept only in task notes; the operator gets no answer. Seen on two feasibility tasks whose notes held nearly complete investigations. Done when a budget stop delivers what the stage found as its outcome detail or plan, or the stage is told it is near the cap and wraps up.
Close reason
Closed
Imported from beads archie-core-gjdh0 · GitHub #1889 · type bug · priority P2 · created 2026-10-26 · closed 2026-10-27
When an agent stage stops at its step budget (e.g. 60/60), the run parks and the work it did is kept only in task notes; the operator gets no answer. Seen on two feasibility tasks whose notes held nearly complete investigations. Done when a budget stop delivers what the stage found as its outcome detail or plan, or the stage is told it is near the cap and wraps up.
### Close reason
Closed
---
_Imported from beads `archie-core-gjdh0` · GitHub #1889 · type bug · priority P2 · created 2026-10-26 · closed 2026-10-27_
sam
added the mediumbug labels 2026-10-27 13:40:00 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When an agent stage stops at its step budget (e.g. 60/60), the run parks and the work it did is kept only in task notes; the operator gets no answer. Seen on two feasibility tasks whose notes held nearly complete investigations. Done when a budget stop delivers what the stage found as its outcome detail or plan, or the stage is told it is near the cap and wraps up.
Close reason
Closed
Imported from beads
archie-core-gjdh0· GitHub #1889 · type bug · priority P2 · created 2026-10-26 · closed 2026-10-27