Recording and replay
Session recording is a Pro feature (terminal.session_recording in features.yml). In the Free edition, Start recording, @record and the palette entry show “Record and replay a tab session is available in the Pro edition.” instead, and replaying a .cast is Pro too.
A recording keeps a tab’s commands and output with their timing, in the asciinema v2 .cast format. Play it back in Termorq or with asciinema play.
Record
Right-click a tab and choose Start recording, or type:
@record startA red dot pulses on the tab while it records. Lines already in the scrollback are not included. @record on its own starts or stops.
Typing @record (or part of a subcommand, such as @record st) lists start, stop, cancel and open in the commands palette, the same way @create and @ssh list their choices. ↑ and ↓ move, Tab completes the word, and Enter runs the highlighted one. While the tab records, stop is listed first, so Enter on a bare @record starts or stops. Choosing @record in the @ palette opens the same list.
Stop and replay
Right-click the tab and choose Stop recording, or type @record stop. The recording is saved to the recordings folder as <tab-title>-<date>T<time>.cast (UTC), and the replay window opens. A name that is taken gets -2, -3 and so on; nothing is overwritten. The folder is Documents/Termorq/Recordings unless you change it in Settings → Record, and it is created when missing.
| Control | What it does |
|---|---|
| Play / Pause | Start or pause playback. Play at the end starts again |
| Seek bar | Jump to a point in the recording |
| Speed | 0.5×, 1×, 2×, 4× or 8× |
| Export .cast… | Save another copy wherever you choose, starting in the recordings folder |
To replay a saved file, type @record open and choose a .cast file. The picker starts in the recordings folder. Files over 20 MB are refused.
From the tray (Pro)
The Termorq tray menu (right-click the notification-area icon on Windows, click the menu-bar icon on macOS) starts with recording rows:
| State | Rows |
|---|---|
| No tab recording | Start recording (red dot), Open recording… |
| A tab recording | Stop recording (stop square), Cancel recording (discard), Open recording… |
Start recording brings the main window up, even when it is hidden or minimised, and records its active tab. Stop recording and Cancel recording act on the active tab when it records, otherwise on the most recent recording, like the shortcut. Stop brings the window up to show the replay; Cancel discards without opening it. Open recording… brings the window up and opens the picker in the recordings folder. The menu switches between the two states whenever recording starts or stops, whether from the tray, the tab menu, @record, the palette or the shortcut. The Free edition has no tray menu, so none of these rows appear there.
Recordings folder
Settings → Record sets the folder. Leave it empty for ~/Documents/Termorq/Recordings, type a full path (or one starting with ~), or choose Browse…. Termorq resolves the path, refuses a relative path or a file, and creates the folder. If saving fails when a recording stops, the replay window still opens, so you can export it by hand.
Cancel and discard
To throw a recording away, type:
@record cancelor press Ctrl+Alt+Shift+R (Cmd+Option+Shift+R on macOS). Recording stops, nothing is saved and the replay window does not open. A short Recording discarded toast confirms it. Nothing is written to disk until a recording stops, so there is no partial .cast file to clean up and nothing lands in the recordings folder. The shortcut acts on the active tab when it is recording, otherwise on the most recent recording. When no tab is recording it does nothing. @record discard is the same as @record cancel.
What is kept out
- Every line goes through the same masking as
@export: tokens, keys, passwords in URLs,Authorizationheaders, andNAME=valuewhere the name looks secret. - The answer after a prompt such as
Password:or[sudo] password for me:is replaced with••••••••. - A line is written only once it is complete, so a secret split across two output chunks is still seen whole.
- A typed command becomes an input marker (
"i"event) only when it had nothing to mask. - Interactive terminal sessions are not recorded. Their keystrokes can be passwords that never reach the scrollback. The recording shows
[interactive terminal session: not recorded …]instead. - Termorq never prints values it resolved from the keychain or a vault. If a program prints one, the masking rules above still apply.