TransIT AI
Sign up

How-tos

Export a session's scrollback

Export saves an SSH session’s scrollback to a file. The bytes are re-redacted on save (PEM blocks, passwords, AWS keys, JWTs stripped), and you can optionally encrypt the file with a passphrase using age.

A shared transcript can’t accidentally leak credentials — even ones that escaped redaction at display time get a second pass on export.

Steps

  1. Right-click the tab in the strip.
  2. Pick Export scrollback…. The Export dialog opens.
  3. Pick an encryption mode:
    • None — writes plaintext .log.
    • Age passphrase — writes .log.age encrypted with the passphrase you supply.
  4. If you chose passphrase encryption, enter the passphrase (twice, to confirm).
  5. Click Export. A native save dialog opens with a default filename derived from the tab’s label and current timestamp.
  6. Pick a location and click Save.

The file is written to disk via Transit AI’s process, not through the browser — no clipboard hop.

Decrypting an age-encrypted export

age -d transcript.log.age > transcript.log

The age binary is on Homebrew (brew install age) and most Linux distros’ package managers. The passphrase prompt matches what you typed in the dialog.

Why re-redact on save?

The redaction filter runs continuously on incoming bytes, but a fresh pass at save time catches anything the streaming filter might have missed:

  • Patterns added since the session opened (we sometimes ship pattern updates in patch releases).
  • Multi-line patterns (PEM, SSH key blocks) that the streaming filter sees in chunks and the save filter sees in full.

The re-redaction is non-destructive in memory — the original bytes in the live terminal pane aren’t modified.

File format

Plain UTF-8. Line endings are preserved as they were in the device output. No metadata header — just the raw redacted scrollback.

For binary-safe export (preserving ANSI escapes, alt-screen state), the file is byte-for-byte what was in the terminal’s scrollback buffer, minus any redactions.