workflow placement: run a workflow transparently on a specified host, local or via swamp workers (incl. nested child workflows)

deprecated extensions are more prominent than I expected :)

swamp serve daemon (user service) doesn't handle systemd 'lingering' — claims it 'starts automatically' but only runs while logged in

Trigger schedule overrides require a swamp serve restart to take effect

swamp serve daemon (user service) doesn't handle systemd 'lingering' — claims it 'starts automatically' but only runs while logged in

swamp cmds don't realise the user is sshed into the system

swamp issue bug isn't auto-filling swamp version, OS and shell

Upgrade/Update causes odd locking issue on swamp deno

stale lock file not being cleaned up?

swamp auth login process fails when run remotely

can the combat log also tell me which hostname the command was run on?

add links to the docs for all account progress teasers

ExtensionWorkflowRepository scans manifest.yaml as a workflow, emitting 'Unknown key manifestVersion' warning

Swamp serve daemon doesn't run with --hot-reload

I _think_ I might like a guard in the trigger yaml

swamp command doesn't check cwd

Output a log line for steps skipped due to guards

Add a --release-notes option to `swamp update` (or even make it the default)

Running "swamp workflow run ..." in a subdir of the swamp repo fails

Pushing an extension after creating a public git repo that is the same as other previously pushed extensions doesn't update the "Verified public repository"

Could not start dynamically linked executable: /home/sven/.swamp/bin/swamp

ln: failed to create symbolic link '/usr/local/bin/swamp': No such file or directory

← Back to list

01Issue

FeatureShippedSwamp CLIPublicTeam

Assigneesstack72

Relationships

#1724 swamp cmds don't realise the user is sshed into the system

Opened by svendowideit · 8/19/2026· Shipped 9/8/2026

Problem Statement

I've been working downstairs, setting up a new computer, and wanted to raise a swamp issue.

so I sshed to my normal computer, and ran 'swamp issue bug' .... and it sat there and did nothing.

when you spawn a new program, you should probably print to the terminal that you are, and what that is (full cmdline?)

cos .... for some other reason, i had EDITOR=code

(hmmm, looking around, this isn't in my bashrc - it might be in some gnome setting or worse)

and ... so my sshed in terminal started vscode without telling me.

Proposed Solution

several - though each will help

tell the user what you're spawning
add a confirmation (yeah, please don't :) )
detect that you're in a terminal that isn't attached to a GUI session - I'm somewhat sure this is plausible - but maybe i'm thinking X11, and yeah, i'm in niri on wayland

clearly the added complexity is that my setting is stupid -

Alternatives Considered

Additional Context

it occurs to me that this has some overlap with #1650

02Bog Flow

Shipped

9/8/2026, 5:40:38 AM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack729/8/2026, 4:56:54 AM

stack72 commented 9/8/2026, 5:40:44 AM

Thanks @svendowideit for reporting this! We shipped: Make every interactive editor launch visible before its child process starts, so SSH and headless users can distinguish an editor wait from a stalled command without relying on platform heuristics.. The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

Sign in to post a ripple.