Tempest Drive — Saved Commands & Scheduled Runs
Find Tempest Drive, save reusable SSH commands, use them across desktop and mobile, and configure interval-based scheduled runs with notifications.
Snippets is now called Tempest Drive. If an older guide tells you to open the “Snippets panel,” open Tempest Drive instead. Your saved commands are Drive documents; you do not need to recreate them because of the name change.
Drive stores reusable commands, scripts, notes and their attachments in your encrypted vault. Save a frequently used SSH command once, then open it on another device or send it to a terminal. You can also run a script on selected hosts and configure recurring runs.
Where to find Tempest Drive
Desktop / web
In the right-hand tool panel, click the cloud icon. Its tooltip and panel title are Tempest Drive. It sits alongside tools such as AI, Tasks, file manager and monitoring.
Desktop / web, panel hidden
Press ⌘⇧P on macOS or Ctrl+Shift+P on Windows/Linux, search for Tempest Drive, and choose Open Tempest Drive to reveal and focus it.
iOS / Android
Open the More tab, then tap Tempest Drive (cloud icon).
iOS / Android, inside a terminal
Open the terminal's session menu and choose Tempest Drive to pick a saved command for that session.
You can also click the search box in the desktop title bar, type > Tempest Drive, and choose Open Tempest Drive. The > switches the palette from host search to commands.
Names are translated with your interface language. For example, the Simplified Chinese label is Tempest 云存储.
Drive is presented as folders and files. On desktop, double-click a document to open it in an editor tab; on mobile, tap it. There is no separate Snippets panel to look for.
Save a command and reuse it across devices
For example, save a command that checks disk space and a service:
df -h
systemctl status nginx --no-pagerCreate it on desktop
Open Tempest Drive using the cloud icon.
Click + → Create. The dialog is titled New document.
Enter a name such as
Check nginx, select Shell (.sh), and optionally enter a folder path such asops / checks.Click Create. The new document opens in an editor tab.
Type or paste the command into the editor.
Save with ⌘S on macOS or Ctrl+S on Windows/Linux.
The creation dialog sets the document's name, language, folder and optional schedule; the editor tab is where you enter its content. Creating and editing Drive documents require Tempest Pro.
For an existing document, double-click it to edit the content. Use Edit (pencil icon) in the editor toolbar to change its name, language, folder or schedule. You can also import files with + → Import files, or drag files into Drive.
Open it on your phone
Sign in to the same account on the same Tempest server, and unlock its vault.
Open More → Tempest Drive.
Navigate to the folder or search for
Check nginx.Tap the document to view or edit it.
On mobile, use Drive's + menu to create a document, enter the command in the editor, then tap Save. The document syncs through the encrypted vault. If it is missing on another device, check the selected account, server endpoint, vault unlock and sync status first.
Send a saved command to the terminal you are using
Desktop
Open the SSH terminal where you want the command to run.
Open the document from Tempest Drive.
In its editor toolbar, choose Send to Terminal. You can also right-click a document in the Drive list and choose that action.
This sends the document text to the active terminal and includes a trailing newline. In a shell, that can execute the command immediately. Check the active terminal and the command content before sending. It uses the existing terminal session; it does not open a new SSH connection.
Choose Copy instead if you want to paste the command yourself and review it before pressing Enter. Sending from the editor uses the content currently on screen; save your edits if you also want them available on other devices.
Mobile
Open the SSH session.
Open its session menu → Tempest Drive.
Tap the saved document and choose Send to session, or choose Copy to paste it yourself.
This session picker is the quickest way to reach a reusable command while you are already connected.
Run a script on selected hosts
Run is different from Send to Terminal: it selects saved destinations and starts a managed execution, rather than typing into the terminal you already have open. This feature requires the multi-run entitlement (Pro).
On desktop:
Open the document and click Run (play icon), or right-click its row in Drive and choose Run.
Select one or more saved hosts in Select run destination, then click Continue.
Choose execution options:
Disconnect after run — close the execution sessions after completion.
AI summary — summarize the results, optionally using a preset or your own instruction.
Notify on failure — send notifications through enabled channels configured on this device.
Click Run. Follow progress in Tasks; each target has its own result. An AI summary opens in the AI panel when enabled.
Use Shell (.sh) for shell commands. Selecting a document language controls its editor presentation; it does not install an interpreter on your server or make a note executable. Attached files are not automatically uploaded or executed as part of the command body. Use commands compatible with the destination and ensure any required programs/files already exist there.
Schedule recurring SSH runs
Configure schedules on desktop / web in the document's Edit dialog. You can also set one in New document, but it cannot run until you have entered and saved a non-empty command body.
Open the document → Edit (pencil icon).
Turn on Enable schedule.
Set Run every, for example
1hour. The minimum interval is 60 seconds; choose seconds, minutes, hours or days.Click Configure targets & options.
Select saved SSH hosts, continue, and configure AI summary, disconnect and notification options.
Confirm the run configuration and save the document properties.
Schedules use an interval, not a cron expression or an “at 03:00” calendar rule. Targets are saved host selections. Current unattended scheduled execution supports SSH hosts; choosing another protocol does not make it a supported scheduled target.
Keep the machine that runs the schedule available
The Tempest backend executes schedules, so a foreground editor window is not required. The backend must still be running, with access to the unlocked vault, target credentials and network.
Desktop: keep Tempest running on an awake computer. Quitting the app, shutting down or putting the computer to sleep prevents execution during that time.
Standalone server / web mode: keep the Tempest backend server running and the account's vault available. Execution does not require a foreground browser window once the account's schedules are loaded.
Syncing the document to a phone does not turn the phone into an unattended scheduler.
This is not a cron job installed on the remote SSH server. Tempest connects to that server when a run is due. The scheduler periodically checks for due work, so an interval is not an exact wall-clock execution guarantee.
Notifications and AI summaries
Set up channels in Settings → Notifications before enabling Notify on failure. The option is disabled when no notification channels are available.
Without an AI summary, failed executions trigger a notification. With an AI summary enabled, the AI can decide whether to notify based on the output and your summary instruction. Delivery uses the device's enabled channels, including local channels and Tempest Push where configured.
For example, an AI summary instruction can ask: “Summarize disk usage and notify me if any filesystem is over 90%.” That requires a configured AI provider and notification channel; review the script's output and summary before relying on it for operational alerts.
Run history
Open the document's History action to inspect retained executions. Run history requires Tempest Pro and can include per-target status/output, timestamps, the command that ran, run options, AI summary and notification content when available.
Run history is different from Vault History: it records executions, while revision history reads retained changes to a saved document from the sync server.
Notes, folders and attachments
Drive also supports PowerShell, Batch, Python, Markdown, AI prompts and plain text. Organize documents with the Folder field, and attach related files using the attachment controls below the editor. Open an attachment in Tempest or with the system application where supported.
Documents and attachments sync through the encrypted vault. Creating, editing, importing, renaming, moving, deleting and attaching files require Pro; browsing existing Drive content is available on every plan. Multi-host execution, scheduled runs and run history also require their corresponding Pro entitlements. AI features require an available provider and the relevant entitlement.
Troubleshooting
“I cannot find Snippets.” Open the cloud icon / Tempest Drive, or More → Tempest Drive on mobile. The feature was renamed.
“I named the document, but it has no command.” Enter its content in the editor after creating it, then save.
“Send to Terminal says there is no active terminal.” Open/select the target terminal first; this action reuses a session rather than choosing hosts.
“The command is missing on my other device.” Check account, server, vault unlock and sync status on both devices.
“The schedule did not run overnight.” Check that the execution machine stayed awake, the backend was running, the vault was available, the script was saved and SSH targets were reachable.
“Run or Edit asks me to upgrade.” Those actions have Pro feature gates; browsing the Drive list does not imply permission to edit or run it on selected hosts.
See also
Last updated