21st help for the full inline usage; a command invoked without its required arguments prints its own usage line. Add --json to most read commands for machine-readable output.
Auth & account
Credential order:
--token/--api-key flag → TWENTYFIRST_TOKEN → API_KEY_21ST → stored login.
Find & install
See Find & install for all search flags.
Bookmarks, lists & teams
Generate with 21st AI
See Generate with 21st AI.
Components & drafts
21st components drains every server page by default. Filter it with
--status all|draft|published|private or
--scope all|personal|team:<uuid>; each row keeps a stable
component:<id> or draft:<uuid> reference for 21st open.
21st open draft:<uuid> resumes an editable Studio draft. 21st open component:<id> creates or resumes a server-owned CLI Review revision from the
retained published component code and demos. The live component stays
unchanged until publish. Fresh covers are required; optional videos run
best-effort in the background. Pass --no-open to create or resume the
workspace and print its editor URL without launching a browser.
Only the original component author can check out code. A Team manager can
still edit or unpublish a teammate’s component metadata by stable ref. Checkout
fails closed when retained source, dependencies, style, support files, or the
default demo cannot be reproduced safely. Use
21st publish <file> --component component:<id> with a local source file
instead.
A login session includes personal work and Teams the user can manage. A
personal key is personal-only; a Team key is restricted to that Team.
New CLI Review drafts persist their authenticated personal or Team/library
scope. Legacy proof-backed CLI drafts are recovered into the matching
authenticated scope. An older unsigned draft whose scope cannot be proven may
need to be recreated.
Publish & manage
Profile
See Your profile.
Design Context & review
See Project-aware design.
Editor & MCP setup
See Editor & MCP setup.