Reaching the step budget asks to continue instead of parking #1832

Closed
opened 2026-11-08 22:28:25 +00:00 by sam · 2 comments
Owner

An agent.run that hits max steps parks with budget_exhausted and the work so far is lost to a fresh attempt. Done when hitting the budget raises an approval request (continue with N more steps, or stop) and an approval resumes the same agent session from where it stopped; declining parks as today.

An agent.run that hits max steps parks with budget_exhausted and the work so far is lost to a fresh attempt. Done when hitting the budget raises an approval request (continue with N more steps, or stop) and an approval resumes the same agent session from where it stopped; declining parks as today.
Author
Owner

Budget stop now waits for approval and continues in the same worktree (e0853403c). Open: approval reruns the workflow from its first step instead of the stopped step, and the model's message history is not restored.

Budget stop now waits for approval and continues in the same worktree (e0853403c). Open: approval reruns the workflow from its first step instead of the stopped step, and the model's message history is not restored.
Author
Owner

Approving a step-budget stop now resumes at the stopped step: the task row carries the resume point and prior step results (existing resume columns, now written on the stop and consumed on resume), so completed steps are skipped. The stopped run's conversation is persisted (new tasks.resume_history, migration 0070), bounded by dropping the oldest tool outputs first, and passed back as request history. agentloop has no prior-messages field, so modelloop renders it as text ahead of the mission, cut to a third of the context window. Rejecting still declines through the cancel path as before. Table test extended: resume skips completed steps and history is passed back; BoundHistory has its own table. task check was clean. Commit dc2c3b983.

Approving a step-budget stop now resumes at the stopped step: the task row carries the resume point and prior step results (existing resume columns, now written on the stop and consumed on resume), so completed steps are skipped. The stopped run's conversation is persisted (new tasks.resume_history, migration 0070), bounded by dropping the oldest tool outputs first, and passed back as request history. agentloop has no prior-messages field, so modelloop renders it as text ahead of the mission, cut to a third of the context window. Rejecting still declines through the cancel path as before. Table test extended: resume skips completed steps and history is passed back; BoundHistory has its own table. task check was clean. Commit dc2c3b983.
sam closed this issue 2026-11-09 01:44:05 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1832