Stats
Actions
Tags
From holyclaude-cloud
Override the legion's max_workers cap at runtime. Useful when you want to push past the ramp, or dial back after seeing throttle.
How this command is triggered — by the user, by Claude, or both
Slash command
/holyclaude-cloud:legion-scale <n>The summary Claude sees in its command listing — used to decide when to auto-load this command
# /legion-scale Set the in-flight worker cap for the current run. --- ## Parse arguments $ARGUMENTS — a single integer N. If no number was given, STOP and use AskUserQuestion: "How many workers? (1-10)" --- ## Procedure 1. Run `~/holyclaude-cloud/bin/legion scale <n>`. 2. Then run `~/holyclaude-cloud/bin/legion cap` and show the user the resulting effective cap. The override persists for the rest of the run. It ignores the ramp but still yields to the throttle observer (if 429s are active, the effective cap is still halved). To clear the override and return to ramp/throttle-only l...
Set the in-flight worker cap for the current run.
$ARGUMENTS — a single integer N.
If no number was given, STOP and use AskUserQuestion: "How many workers? (1-10)"
~/holyclaude-cloud/bin/legion scale <n>.~/holyclaude-cloud/bin/legion cap and show the user the resulting effective cap.The override persists for the rest of the run. It ignores the ramp but still yields to the throttle observer (if 429s are active, the effective cap is still halved).
To clear the override and return to ramp/throttle-only logic: legion scale <config_max_workers> (default 5). There isn't a "reset to auto" yet — Phase 4 polish.
/legion-status for a few minutes after scaling up.npx claudepluginhub ajsai47/holyclaude-cloud