Use agent.maxSteps for cron step budget instead of hardcoded 30#113
Merged
tsubasakong merged 2 commits intomainfrom Mar 17, 2026
Merged
Use agent.maxSteps for cron step budget instead of hardcoded 30#113tsubasakong merged 2 commits intomainfrom
tsubasakong merged 2 commits intomainfrom
Conversation
Cron tasks were aborting mid-execution because the step budget defaulted to 30 (clamped 20-60), far below the configured agent.maxSteps of 100. This caused tasks like "comment on 10 posts" to fail after only 6. - Default cron stepBudget now uses config.agent.maxSteps - Clamp range changed from 20-60 to 80-agent.maxSteps - LLM planner prompt updated to reflect new range - Remove redundant stepBudget fallback in attempt.ts guidance builder Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Use
config.agent.maxStepsfor cron step budget instead of hardcoded 30.Why
Cron tasks were aborting mid-execution because the step budget was hardcoded to 30 (clamped 20-60), well below the configured
agent.maxSteps(default 100). For example, a "comment on 10 posts" task would abort after only 6 comments at step 30.Changes
stepBudgetnow usesconfig.agent.maxStepsinstead of hardcoded 30agent.maxStepsattempt.tsguidance builder, trusting the already-normalized value from upstreamTesting
tsc --noEmit— passes cleanlyChecklist
🤖 Generated with Claude Code