Enable Workflows and install runtimes
Switch Workflows on and confirm that the runtimes you plan to use are on PATH. Time: 10 minutes. Needs: Termorq Pro (or Trial).
Free builds don’t offer the experimental flag or the Workflows page. The edition pill (FREE, TRIAL, or PRO) is at the right of the header.
Steps
- Open Settings → Experimental.
- Turn on Workflows. It is off by default.
- Open the page with Cmd+Shift+G (macOS) or Ctrl+Shift+G (Windows/Linux). You can also open the jump list with Ctrl+J and choose Workflows, or type
@flow.
If you later turn the flag off, Termorq hides the page’s entry points and workflow settings. A workflow that is already open stays open until you leave it.
Check your runtimes
Termorq doesn’t bundle language runtimes. The code runner uses whatever is installed on your computer. Run these commands in a Termorq terminal tab:
| Language | Needs |
|---|---|
| Bash | bash on PATH. Workflow Bash is always Bash, even if your terminal tab runs another shell. |
| PowerShell | pwsh (runs with -NoProfile -NonInteractive -ExecutionPolicy Bypass) |
| Python | Python 3 as python3 or python (runs unbuffered with -u) |
| C# | .NET SDK 10+ (single-file app via dotnet run) |
| Rust | rustc with edition 2024 (--edition 2024 -O), without Cargo |
| JavaScript | Node.js (runs as an ES module, snippet.mjs) |
| TypeScript | Node.js 22.6+ native type stripping, or a tsx executable |
If you install a runtime while Termorq is open, restart Termorq so it can find the runtime.
The Workflows page opens and lists at least the Included workflows, such as Refresh Acme users and Probe mock. Each runtime you plan to use prints a version.
Find out which Node.js version you have. Will TypeScript blocks run natively, or will they need tsx?
Reference: Node types and code languages