TranscriptDocs
Console

Authentication

transcript login

Shell
transcript login

This starts a device-authorization flow (the same shape as gh auth login or docker login):

  1. The CLI shows a short code (e.g. WDJB-MJHT) in your terminal and opens your browser (or prints the link, if it can't open one automatically).
  2. You confirm that code on transcript.land/device, signed in as yourself.
  3. Once you confirm, the CLI receives your API key and stores it.

No new token type is involved — the key the CLI receives is the same sk_live_... key shown in Settings. If you already have one, confirming rotates it (the old value stops working, same as clicking "Regenerate" in Settings) so the CLI gets a live credential.

The key is stored at ~/.config/transcript/config.json, mode 0600.

transcript logout

Shell
transcript logout

Removes the stored key from ~/.config/transcript/config.json. Other saved preferences are kept.

How credentials are resolved

For every command, in this order:

  1. --api-key <key> flag
  2. TRANSCRIPT_API_KEY environment variable
  3. The key saved by transcript login

If none are set, get still works, but as an anonymous request — capped to a short preview (see Introduction).

Using a different API base (e.g. staging)

Shell
export TRANSCRIPT_API_BASE=https://staging-api.transcript.land

Overrides the config file's api_base, which defaults to https://api.transcript.land.