RUN mode
§ RUN
RUN gives you real terminals inside the workspace — actual PTYs driven by a persistent daemon, not a sandboxed emulation. Run builds, tests, dev servers, REPLs, anything you would run in your own shell. The output is real because the process is real.
Because the daemon outlives the app window, your sessions survive an app restart and reattach automatically.
How to open it
Section titled “How to open it”Press ⌘⇧2, or click Run in the mode switcher. RUN is always present in every workspace.
[screenshot: RUN mode with a running dev server and the terminal list in the Companion]
The interface
Section titled “The interface”Each workspace can hold multiple named terminals. Switch between them with ⌘⌥1 through ⌘⌥9. Each terminal is a full xterm.js surface, so colors, cursor movement, and interactive TUIs render correctly.
When a command prints a file path, RUN turns it into a clickable link. Clicking it jumps straight to that file in REVIEW — handy for stack traces and linter output.
The Companion panel lists every terminal in the workspace with its status, so you can see at a glance which sessions are live, idle, or were restored.
Sessions survive restart
Section titled “Sessions survive restart”The terminals are backed by a persistent daemon. Quit Octopush — or let it crash — and your running processes keep their state. On relaunch, RUN reattaches to the live sessions and marks each one with a “Restored” badge.
[screenshot: a terminal showing the “Restored” badge after relaunch]
A typical flow
Section titled “A typical flow”- Open a workspace and press
⌘⇧2. - Start a dev server in the first terminal.
- Open a second terminal with a new tab and run your tests there; switch between them with
⌘⌥1/⌘⌥2. - A test fails and prints a file path — click it to jump to that line in REVIEW.
- Quit Octopush for the day. Reopen it tomorrow: the terminals come back with a “Restored” badge.
Shortcuts
Section titled “Shortcuts”| Shortcut | Action |
|---|---|
⌘⇧2 | Switch to RUN |
⌘⌥1–⌘⌥9 | Jump to terminal 1–9 |