All pages
Docs · Background features
Sharing & export
Availability: macOS.
TRMNLY supports two flavors of sharing beyond the settings bundle: terminal transcripts (File menu) and agent sessions (agent sidebar).
Share Session
File → Share Session…
Snapshots the focused tab's scrollback, runs the transcript sanitizer over
it, and uploads it to GitHub as a secret gist using your gh CLI. The
gist URL lands on your clipboard, ready to paste.
Before anything uploads, a confirmation shows the transcript length and how many redactions were applied — cancel there if something looks off.
Why gh instead of a hosted service: your GitHub auth handles identity and
revocation, and there's no TRMNLY backend involved. Gists are secret (not
public) by default, and revoking a share is one gh gist delete away. If
gh isn't installed or authenticated, the share stops with instructions.
Export Tab Transcript as .cast
File → Export Tab Transcript as .cast…
Writes the focused tab's scrollback as an asciinema
.cast v2 file. The export is a single frame — an instant text dump of the
screen contents, not a timed recording — so it plays as a static transcript
via asciinema play, and converts to SVG/GIF with tools like agg or
svg-term.
This path does not run the sanitizer — review the scrollback before you share the file.
Share an agent session
From the management menu in the agent sidebar:
- Export as Markdown… / Export as JSON… — save the conversation directly to a file.
- Share session… — build a scrubbed copy of the session (messages, tool calls, tool results) and preview every redaction before anything is written. Pick Markdown or JSON, choose whether tool results are included, and save. Nothing uploads automatically — you decide where the file goes.
The /share command in the trmnly-code REPL produces the same redacted
output.
What's redacted automatically
The gist path and the agent-session share both scrub secrets by pattern before anything leaves the app:
- Provider API keys — Anthropic (
sk-ant-…), OpenAI (sk-…), Stripe live keys - GitHub tokens (
ghp_…and friends) and Slack tokens (xox…) - AWS access key ids (
AKIA…) - JWTs and PEM private-key blocks
KEY=valuepairs whose name looks sensitive (…_API_KEY,…_TOKEN,…_SECRET,PASSWORD=, …)
Each match is replaced with a <REDACTED:…> marker and counted, and you see
the count before sharing. The scrubber is conservative by design: a false
positive redacts a token, never the surrounding context. It's a heuristic —
still worth a skim before you send anything sensitive.
Privacy footprint
Nothing is shared without an explicit action and a confirmation. Share
Session uploads to your GitHub account as a secret gist; the .cast and
agent-session exports are plain local files until you send them somewhere.