CLI reference

The lerpa-cli package copies components and blocks from the registry into your project. Both binary names work: lerpa and lerpa-cli. Run it without installing via pnpm dlx, npx, or bunx.

init

Initialize Lerpa UI in your project. Detects your package manager, prompts for your CSS path, Tailwind config path, and import aliases, then writes lerpa.json and creates a cnhelper if one doesn't exist. Run this first.

add <name>

Fetch and install a single component or block by its registry id, resolving any registry dependencies. The source is written into components/ui (or components/blocks for blocks).

Flags

-y, --yes

Skip the confirmation prompt and write files immediately.

list

List every available item in the registry, grouped into atomic UI components (registry:ui) and interactive blocks (registry:block), with their dependencies.

search [query]

Search the registry by name. With no query it returns everything; with a query it filters to matching ids. Useful for discovering the right add id from the terminal.

update [name]

Re-pull components to their latest registry versions. Pass a name to update one component, or omit it to scan your components/ui and components/blocks folders and update every installed item.

theme

Apply a color theme's CSS-variable values into your global stylesheet. For a visual, interactive alternative, use the Theme Studio.

doctor

Run diagnostics on your setup — verifies that lerpa.json exists and that the configured CSS, Tailwind, and alias paths resolve. Handy when addisn't writing where you expect.

info

Print CLI metadata (version, license, repository, docs) and, if present, your local project's resolved aliases.

Configuration details live in Configuration, and the same registry powers the MCP server for AI agents.