Visual workflow
The workflow board groups open connections into named steps. Use it to organise maintenance, troubleshooting or daily checks, with an optional Flash Command assigned to each step.
Configure your process
- Expand the workflow board using the arrow in its header.
- Open the adjacent three-dot menu and choose Configure workflow.
- Add, name and reorder steps. For a daily check, try To check → Disk space → Failed services → Reviewed.
- Associate your saved
df -hcommand with Disk space andsystemctl --failed --no-pagerwith Failed services on Linux hosts that use systemd. Leave To check and Reviewed without commands. - Save the configuration. Enable confirmation in the Flash Command settings for commands that need review.
These are example steps and commands: adapt them to your hosts and procedures.
Work through the steps
Open your server connections. New connections appear in the first step without running its command. Drag an open SSH connection card to Disk space to send that step’s command to its existing terminal. Inspect the output before moving to Failed services, then move to Reviewed when you have completed your checks.
Selecting a card or tab displays its connection. Selecting, reordering tabs or editing workflow configuration does not send a command. If a command requires confirmation, cancelling leaves the card in its original step.
You can also drag a device from the catalogue directly into a workflow step. Its default connection opens there; an assigned entry command is sent after a new SSH connection opens, with confirmation when configured.
Understand the result
The board records where you place connections. It does not automatically verify remote command success or advance hosts to the next step. SuperCharged reports whether input was sent: check the terminal output to determine the result.
Commands go to the terminal’s foreground process. Make sure the shell is ready; an editor, interactive program or password prompt can receive the input instead. Commands are not sent to non-SSH or disconnected sessions. Connections are not automatically reopened. When sending fails on an SSH connection, a retry is available.
The terminal stays open regardless of the Flash Command’s close-on-finish setting, although a script can explicitly close it.
Reuse the setup
Step names, order and command associations are saved locally and included in configuration export. Open connections and their positions are not restored after restart. Removing a step and saving closes its open connections.

