Words, tables, charts and code on one clean page: a tale. Your AI drafts it, you approve it, and anyone with the link can read it. No account needed.
$ npx -y taleseal@latest init claude
# sets up Claude Code and publishes a live test page$ npx -y taleseal@latest init codex
# sets up Codex and publishes a live test page$ npx -y taleseal@latest init cursor
# sets up Cursor and publishes a live test pageOne command. It sets up your tool and publishes a live test page before you even have an account.
For your reviewer
Where the 800 ms went, and the two changes that reclaimed it.
Checkout p95 sat at 1.9 s, and 800 ms of it was one repeated basket query. That fix, plus a cache header, brings p95 under 1.1 s with no spend.
| Change | Effect |
|---|---|
| Batch the basket lookup into one query | −720 ms at p95 |
| Cache the delivery options for 60 s | −80 ms at p95 |
free · no card · readers need no account
What a tale is
It replaces the long write-up nobody enjoys writing and nobody quite reads, whether it goes to a customer or your own team.
Something needs explaining
A customer asks why checkout is slow. A decision needs a write-up people will actually read. A job just finished and someone will ask what happened. You say: “write this up as a page.”
Your AI drafts the tale: a page, not a chat log
Real words, tables, charts, diagrams, code and images, with the sources it drew on shown. It lands at its own private link, marked DRAFT, seen only by people who hold that link.
You review, it revises, you publish
Ask for changes in plain words and the same page updates. Publish when it reads right, then send the link. It stays the same through every revision, and the reader needs no account.
It reads like you spent the afternoon on it. You spent a minute reviewing it.
See the block galleryWhere a tale goes
In a pull request
“Why this approach?”Answer with the tale: the reasoning, the numbers and the code on one page, next to the diff instead of scattered through a thread.
In Slack
“What happened with the migration?”Paste the link. It unfurls with the title, and whoever clicks gets a page they can read in thirty seconds, not a scrollback.
On a schedule
“Nobody watched it run.”Unattended jobs draft their own report with --yes. You read the page over coffee and decide whether it publishes.
When you’re ready
Run npx taleseal login and approve in the browser that opens. It creates your account on the way and saves a key on your machine, so you never type it again.
npx taleseal draft tale.json shows exactly what it is about to send, waits for your yes, then prints the private draft link. Review it in the browser; ask for changes in plain words.
One more command takes the DRAFT banner off. Paste the link in Slack, the pull request or an email. Whoever opens it needs no account.
Working in an AI coding tool? Point it at taleseal.com/integrate and it can set itself up and draft the first page end-to-end.
Your call, always
A tale starts as a draft only you know the address of, and nothing reads “published” until you say so. Every link is unguessable, opens without an account, and never shows up in search.
Change your mind at any time: retracting a tale destroys every version at once, and the address answers 410 Gone, permanently.
taleseal.com/t/9fK2aBw7Qc4m
your reviewer requested changes
Why this approach?