Skip to main content
← Back to list
01Issue
FeatureShippedSwamp Club
Assigneesstack72

Relationships

#991 Docs: add --concurrency flag and SLOTS column to worker-commands reference

Opened by stack72 · 7/6/2026· Shipped 7/6/2026

Summary

Phase 4b (#989) added capacity slots (--concurrency N|auto) and least-loaded scheduling. The worker-commands reference page needs updates.

Change needed

`content/manual/reference/remote-execution/worker-commands.md`

`swamp worker connect` section — add flag to the flags table:

Flag Required Description Default
`--concurrency ` No Number of concurrent dispatch slots (`auto` = CPU count, min 1). A capacity-4 worker runs up to 4 steps simultaneously, each in its own isolated child process. (env: `SWAMP_WORKER_CONCURRENCY`) `1`

Add env var:

Variable Flag
`SWAMP_WORKER_CONCURRENCY` `--concurrency`

Add example: ```bash

Big node: 8 concurrent dispatch slots

swamp worker connect wss://orch:9090 --token --concurrency 8

Auto-detect from CPU count

swamp worker connect wss://orch:9090 --token --concurrency auto ```

`swamp worker list` section — note that the output now includes a SLOTS column showing current load (e.g., `0/4`, `3/8`). JSON output includes `capacity` (number) and `activeDispatchIds` (array).

Files verified as needing NO changes

  • `reference/swamp-serve/serve-flags.md` — capacity is worker-side
  • `reference/remote-execution/enrollment-tokens.md` — no token changes
  • `reference/remote-execution/failure-semantics.md` — no failure behavior changes
  • `reference/remote-execution/security.md` — per-dispatch credential scoping is internal

Context

Ship alongside or shortly after #989 merges.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 2 MOREREVIEW+ 3 MOREPR_MERGED+ 1 MORENOTIFICATION_SKIPPED

Shipped

7/6/2026, 7:15:10 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack727/6/2026, 6:52:37 PM

Sign in to post a ripple.