Skip to main content
← Back to list
01Issue
FeatureOpenSwamp CLIPublic
AssigneesNone

Relationships

#4871 Docs: enrollment token rotation now reaches workers from workflows, schedules and local rotate

Opened by zack · 11/18/2026

swamp-club#4861 changes what the manual says about rotating worker enrollment tokens.

  1. content/manual/reference/remote-execution/enrollment-tokens.md says a local rotation (no --server) reaches no worker. After #4861 a running orchestrator sends it to connected workers at its next token check, about every 30 seconds, the same way a local revoke reaches them. Only workers on the token's previous mint receive it; a second rotation before that check still retires them.
  2. content/manual/how-to/worker-fleets/rotate-enrollment-tokens.md covers only rotating through --server. Add a section on rotating on a schedule: a workflow with one model_method step (modelIdOrName set to the token name, methodName rotate, optional durationMs) triggered by a schedule on serve, with the note to space rotations more than a minute apart and that only --server returns which workers were not rotated (serve logs them otherwise). This is the reporter's use case in #4861: one worker per host, weekly rotation under --remote-only, with no external CronJob or admin server token.
  3. content/manual/reference/remote-execution/worker-commands.md: the rotate entry should say, as revoke's does, that without --server a running orchestrator acts at its next token check.
02Bog Flow
◉OPEN○TRIAGED○IN PROGRESS○SHIPPED

Open

11/18/2026, 3:31:01 PM

No activity in this phase yet.

03Sludge Pulse
Editable. Press Enter to edit.

zack commented 11/18/2026, 5:40:50 PM

Update from the final #4861 change (PR swamp-club/swamp#3853), which changes what the manual pages need to say:

  1. Default rotation lifetime. A rotation without --duration (or a workflow rotate step without durationMs) now gives the new token the token's lifetime plus the old token's remaining time, capped at a tenth of the lifetime and at least 40 seconds. A schedule as long as the token's lifetime therefore never lets it lapse, and rotating more often never extends a credential beyond its lifetime plus that cap. An explicit --duration / durationMs still counts from the rotation.
  2. Delivery timing. A rotation made by a workflow step or schedule on serve reaches connected workers as soon as the step finishes. A rotation without --server from another process (the local CLI) reaches them at serve's next token check, about every 30 seconds; the CLI warns when the old token expires before that check could deliver it and points at --server.
  3. The scheduled-rotation how-to can recommend the simplest form: a schedule trigger with the token's lifetime as its period and a rotate step with no inputs.

Sign in to post a ripple.