Skip to content

feat(auto-engineer): make plan/implement turn and budget limits configurable per run #101

Description

@toufali

Problem: The auto-engineer's per-phase turn and budget caps are hardcoded — config/defaults.yml (max_plan_turns: 20, max_plan_budget_usd: 1.50, etc.) with defaults baked into scripts/run-claude.sh (MAX_CLAUDE_TURNS, MAX_BUDGET_USD). They aren't exposed on the workflow_dispatch, so there's no way to raise them for a single run from the Actions UI.

A plan run on #99 hit the cap and exited with code 1 and 0 lines of output ("likely hit max-turns or budget"), with no self-serve way to give it more room — see run https://github.com/mozilla/blender/actions/runs/30034409270. This was the main thing blocking us from using the auto-engineer.

Proposal: Add optional workflow_dispatch inputs — e.g. max_turns and max_budget_usd — that override the per-phase defaults, plumbed through to MAX_CLAUDE_TURNS / MAX_BUDGET_USD in run-claude.sh. Empty/unset falls back to config/defaults.yml (current behavior).

Acceptance: Can bump the plan/implement turn and budget limits for a single dispatch from the Run-workflow form without editing the repo.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions