Getting started
Seal your first run.
One command turns an agent run into a shareable page — the trigger, what it read, the decisions it took and set aside, and the outcome. You see a preview before anything leaves your machine.
npx taleseal sealfree · readers need no account · preview needs no key
Pick your tool
Install once, then seal from where you already work.
/plugin marketplace add Taleseal/taleseal
/plugin install taleseal@talesealThen /taleseal:seal — or just say “seal this session”.
codex plugin marketplace add Taleseal/taleseal
codex plugin add taleseal@talesealThen ask Codex to “seal this session”.
npx -y taleseal login
npx -y taleseal sealAlso --codex for Codex rollouts and --preview to dry-run with no key.
Coming soon — the CLI’s Cursor session reader is in progress.
How it works
Four steps — and the third is where the trust is.
From a plugin or the CLI, after a run. It reads the session on your machine — nothing is sent yet.
The composed tale, plus a redaction report of anything the scanner caught. All still local.
Only on your yes does it leave your machine. You get back one short, unguessable link.
In the PR or the Slack thread. Anyone can open it — no account needed to read.
Signing in is one command
npx taleseal login opens the browser: approve there (signing up on the way if needed) and an API key is created and saved on your machine automatically. Skip even that — the first seal signs you in on the spot. Previews and dry-runs need no key at all; the key is only for publishing. On CI, mint a key in the dashboard and set TALESEAL_API_KEY.
Keep going