Snippets
Save commands once, run them in any session or across whole groups of machines, and review execution history.
A snippet is a saved command (or script) with a name and an optional remark. Snippets live in the Snippets section of the sidebar and can be organized into packages.
Create a snippet
- Open Snippets and choose New Snippet (or New Package to group related snippets first).
- Give it a Name, paste or write the Code (the editor highlights shell syntax), optionally pick a Package and add a remark.
- Save.
Snippets run exactly as written — what you see is what executes.
Run in a terminal session
Open the terminal inspector and switch to the Snippets tab. It lists your packages and snippets, searchable by name. Every snippet has three buttons:
- Copy — copy the code to the clipboard.
- Paste — type the code into the session without running it, so you can edit before pressing return.
- Run — type the code and press return in one tap.
This works in SSH and Mosh sessions alike.
Run across many machines
From a snippet's detail page, tap Execute Snippet:
- Select any mix of Machines and Groups — selecting a group targets every machine in it.
- Confirm with Execute on X machines and Y groups.
Each machine gets its own one-shot SSH connection running the snippet non-interactively, with a per-machine timeout of 15 seconds by default (Settings → Resources → Snippet Execution Timeout, 5–60 seconds). The Execution Result screen shows a card per machine — green check or red cross, with the captured output a tap away. Every run is also saved to Snippet Execution History.
Quiet commands read as failures
A run counts as successful when the command prints something to stdout. A
command that succeeds silently (for example a bare
systemctl restart) is reported as failed — append a quick
confirmation like && echo ok to make the result explicit.