Skip to content

feat(agent): max_iterations joins the reserved agent-node inputs - #65

Merged
wolfy-j merged 1 commit into
masterfrom
feat/agent-max-iterations-input
Aug 8, 2026
Merged

feat(agent): max_iterations joins the reserved agent-node inputs#65
wolfy-j merged 1 commit into
masterfrom
feat/agent-max-iterations-input

Conversation

@wolfy-j

@wolfy-j wolfy-j commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

The agent node reserves the inputs context, model, and agent_id; the iteration budget was the one arena dial with no runtime carrier, so a workflow-lowered agent node always ran at the configured or default cap regardless of what the operator dialed.

max_iterations is now the fourth reserved input: a positive integer overrides arena.max_iterations for the run; anything else is rejected as input validation; absent keeps existing behavior. It renders no prompt tag, same as the other reserved carriers.

Tests: 961 sqlite suite green (reserved-input unit cases extended, plus a validation case).

A workflow payload can now carry the iteration budget the way it carries
context, model, and agent_id: a positive-integer max_iterations input
overrides the arena config; absent keeps the configured or default cap.
@wolfy-j
wolfy-j merged commit 35cf94d into master Aug 8, 2026
8 checks passed
@wolfy-j
wolfy-j deleted the feat/agent-max-iterations-input branch August 8, 2026 19:10
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.

1 participant