Relationships
#2748 workflow reference.md documents removed --driver flag on swamp workflow run
Opened by yeungonion · 9/30/2026· Shipped 9/30/2026
Description
The workflow skill's reference.md Quick Reference / "Run a Workflow" section
documents a --driver <driver> flag on swamp workflow run:
| --driver <driver> | Override execution driver for all steps (e.g. raw, docker) |
This flag no longer exists. swamp workflow run --help shows no --driver
option. remote-execution.md in the same skill confirms why:
"It replaces the removed execution-driver abstraction (driver:/driverConfig:
fields no longer exist); for isolation, run a containerized worker and select
it with labels."
The two docs contradict each other about whether per-step Docker isolation is driver-based or worker+labels-based, which is confusing when designing container-level isolation for workflow steps.
Steps to Reproduce
- Read the swamp workflow skill's reference.md —
--driveris documented. - Run
swamp workflow run --help— no--driverflag is present. - Read remote-execution.md — confirms the execution-driver abstraction was removed.
Environment
- swamp version: 20260811.225020.0-sha.84041051
- Platform: linux
Suggested Fix
Remove the --driver row from reference.md's "Run a Workflow" options table
(and any other stale mentions of driver/driverConfig), and add a
forward-pointer to remote-execution.md's worker+labels model wherever
step-level isolation is discussed.
Shipped
Click a lifecycle step above to view its details.
stack72 commented 9/30/2026, 2:28:40 PM
Hey @yeungonion
We don't support the drivers work - we now support remote execution instead https://swamp-club.com/manual/how-to/swamp-serve/set-up-remote-only-orchestrator
I will clean up that doc now
stack72 commented 9/30/2026, 9:26:42 PM
Thanks @yeungonion for reporting this! We shipped: Remove stale references to the removed execution-driver feature from the bundled swamp skill, README, and one help string: the driver flag on model method run, the drivers manifest field docs, the extensions/drivers dir and driversDir key, and the execution driver wording on method_execution_failed. Reword trace-propagation docs from Docker drivers to remote workers. Intentional mentions (removed-field guards, manifest deprecation warning, remote-execution.md, design history) stay.. The fix has been merged and a release is on its way. We appreciate your contribution to swamp.
Sign in to post a ripple.