Getting started

One command to a live page.

init sets up your tool and publishes a live test page (a tale) before you even have an account. From then on, ask your AI to “write this up as a page”: it drafts at a private link, you review in the browser and publish when it reads right. Readers need no account.

Shell
npx -y taleseal@latest init

free · readers need no account · validate needs no key

Pick your tool

Install once, then ask from where you already work.

Claude Codeplugin
Shell
npx -y taleseal@latest init claude

Installs the plugin from the marketplace and publishes a live test page. Then just say “write this up as a page”.

Codexplugin
Shell
npx -y taleseal@latest init codex

Installs the plugin from the marketplace and publishes a live test page. Then ask Codex to “write this up as a page”.

Cursorcli
Shell
npx -y taleseal@latest init cursor

Publishes a live test page and prints the plugin steps for Cursor. The agent composes tale.json; draft puts it at a private link.

›_CLI · any toolnpm
Shell
npx -y taleseal@latest init
npx -y taleseal draft tale.json

Creates the tale as a private draft and prints its link; validate checks the JSON with no key. On CI, set TALESEAL_API_KEY and pass --yes.

{ }The SDK · TypeScriptnpm
Shell
npm install @taleseal/sdk

For anything you build yourself. draftTale() creates the page at its private link, reviseTale() stores the next draft behind it, and publishTale() makes it the version readers see. The full surface, and how to hand it to an AI coding tool, is documented at taleseal.com/integrate.

How it works

Ask, draft, review, send.

01
Ask

Tell your AI what needs explaining. It writes the page (words, tables, charts, code) as tale.json.

02
Draft

draft shows you exactly what it is about to send, secrets redacted, and waits for your yes. Then it prints the private draft link.

03
Review & publish

Open the draft in the browser. Want changes? Ask in plain words and the same page updates. Publish when it reads right.

04
Send the link

In the PR, the Slack thread or an email. The address never changes across revisions, and readers need no account.

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. validate needs no key at all; drafting and publishing do. On CI, mint a key in the dashboard and set TALESEAL_API_KEY.

Keep going