Skip to content

Remove --max-turns limits from issue_solver and pr_followup #456

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stbenjam merged 1 commit into from
Jul 26, 2026
Merged

Remove --max-turns limits from issue_solver and pr_followup #456

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion .github/workflows/skillsaw-issue-solver.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,7 +133,6 @@ jobs:
show_full_output: true
claude_args: |
--dangerously-skip-permissions
${{ !matrix.issue.ultracode && '--max-turns 200' || '' }}
--model ${{ matrix.issue.fable && 'claude-fable-5' || 'claude-opus-5' }}
${{ matrix.issue.ultracode && '--effort ultracode' || '' }}
Comment on lines 134 to 137

@qodo-code-review qodo-code-review Bot Jul 26, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remediation recommended

2. Removed max-turns cap 🐞 Bug ☼ Reliability

The Issue Solver and PR Follow-up workflows no longer pass explicit non-ultracode --max-turns caps
(previously 200 and 100 respectively), removing a turn-budget guardrail and allowing substantially
longer Claude runs than before. Because both are scheduled and share concurrency: skillsaw-agent
with cancel-in-progress: false, unusually long runs can serialize the queue and delay other agent
workflows from starting.
Agent Prompt 
## Issue description
The Issue Solver and PR Follow-up workflows removed the explicit `--max-turns` guardrail for non-ultracode runs, so the Claude steps can take much longer than they used to and potentially run unbounded.

## Issue Context
Both workflows are scheduled every 15 minutes and share a single concurrency group (`skillsaw-agent`) with `cancel-in-progress: false`, which means long-running executions serialize the pipeline and can delay subsequent scheduled agent work (including later Issue Solver runs and PR follow-ups).

## Fix Focus Areas
- .github/workflows/skillsaw-issue-solver.yml[3-11]
- .github/workflows/skillsaw-issue-solver.yml[100-138]
- .github/workflows/skillsaw-pr-followup.yml[3-11]
- .github/workflows/skillsaw-pr-followup.yml[128-170]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Expand Down
1 change: 0 additions & 1 deletion .github/workflows/skillsaw-pr-followup.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,6 @@ jobs:
show_full_output: true
claude_args: |
--dangerously-skip-permissions
${{ !matrix.pr.ultracode && '--max-turns 100' || '' }}
--model ${{ matrix.pr.fable && 'claude-fable-5' || 'claude-opus-5' }}
${{ matrix.pr.ultracode && '--effort ultracode' || '' }}

Expand Down