Sharing sessions

polyglot share turns a session into a readable file you can paste into a pull request, drop in an issue, or attach to a bug report.

polyglot share                       # the most recent session -> ./polyglot-session-<date>.md
polyglot share <id>                  # a specific session by id (from /status or the -p envelope)
polyglot share ./saved.jsonl         # a session file someone sent you
polyglot share <id> --format html --out review.html

export is an alias for share. In the TUI, /share does the same for the current session (/share --html, /share --full, /share <path>).

Redaction

Secret-looking values are scrubbed by default: cloud access keys, sk-… / sk-ant-… keys, GitHub tokens, Bearer … tokens, PEM private-key blocks, and SOMETHING_KEY = "…" assignments. A tool call that reads a secret file (.env, *.pem, anything under .ssh/) and its result are blanked entirely. The export tells you how many values it redacted.

This is a safety net, not a guarantee - it will miss bespoke secrets. --no-redact turns it off. Either way, the raw session file on disk is never modified - only the export.

Format

	Markdown (default)	HTML (--format html)
Tool calls	one-line summaries (→ read_file(app.ts))	same
Result bodies	omitted unless --full	omitted unless --full
Self-contained	yes	yes - inline CSS, no external requests

--full includes complete tool-call arguments and result bodies in either format.

Flag	Default
--out <path>	./polyglot-session-<date>.<ext>	output file
--format <md|html>	md
--no-redact	off	keep secret-looking values
--full	off	include full tool IO

Resuming from a shared file

--resume accepts a path to a .jsonl session file, not just an id:

polyglot --resume ./teammate-session.jsonl

so a colleague can hand you a session and you pick up where they left off. (Resuming from a redacted .md export isn’t supported - it’s lossy by design. Share the .jsonl, or a --full --no-redact export, for that.)