Skip to content

Fix #393: enforce accurate timeout budgets in agent chains#398

Closed
yxlyx wants to merge 1 commit intomainfrom
fix/393-accurate-timeout-budgets
Closed

Fix #393: enforce accurate timeout budgets in agent chains#398
yxlyx wants to merge 1 commit intomainfrom
fix/393-accurate-timeout-budgets

Conversation

@yxlyx
Copy link
Copy Markdown
Collaborator

@yxlyx yxlyx commented Apr 2, 2026

Summary

  • enforce exact per-step timeout budgets in run_task chains so sub-second remainder does not get rounded up into an extra second of wait time
  • keep timed-out worker cleanup safe in runChainStep and expose timeout_seconds on run_explorer and run_task
  • add timeout-focused tests for budget expiry and timeout payload reporting

Testing

  • zig fmt --check src/tools.zig
  • zig build test (blocked locally by the current Zig/macOS linker environment: unresolved Darwin libc symbols before project code runs)

Closes #393

@yxlyx
Copy link
Copy Markdown
Collaborator Author

yxlyx commented Apr 4, 2026

Superseded by #402, which reapplies the remaining timeout-budget work onto current main after #400.

@yxlyx yxlyx closed this Apr 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: create_issue parent_issue claims subtask semantics but only appends body text

1 participant