Remove the maximum for the number of concurrent agents - #1692
Merged
Conversation
…un at once is the user's call The sanitizer still rounds and floors the count at one — zero is what the Auto PM switch already spells — but no longer caps it, and the routine panel's box and the AI Queue's fan-out count drop their upper bound with it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012iYzJdkGec61jKo85tyipK
Contributor
|
LGTM. The 8 daemon failures = no |
Contributor
Author
|
Confirmed — after Generated by Claude Code |
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
3 participants
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.
The concurrent-agents count (
autoPmConcurrency, #1204) was capped at 10 byMAX_AUTO_PM_CONCURRENCY. The cap is gone: how many agents to run at once is the user's call, and the week's allowance is what actually paces unattended work.What changed:
MAX_AUTO_PM_CONCURRENCYdeleted frompreference-defaults.ts, along with its re-exports (registry.ts,client.ts).autoPmswitch already spells), but no longer clamps it from above.maxattribute and upper clamp; the floor at one stays.preference-defaults,registry,registry.test,RoutineWork,RoutineWork.test,AiQueue). No FEATURES-SPEC.md change: the concurrency setting itself remains a feature, only its value's upper bound is removed.Validation: typecheck passes; registry node tests 59/59; full dashboard vitest suite 834/834; full node suite green. (The 8
daemon.test.tsfailures first seen were a missingdist/in the fresh checkout — afterpnpm build,daemon.test.tspasses 15/15.)🤖 Generated with Claude Code
https://claude.ai/code/session_012iYzJdkGec61jKo85tyipK
Generated by Claude Code