Registry Workflows

This page collects the LPM CLI commands that connect to LPM.dev Registry services. For the complete command and flag reference, use cli.lpm.dev/docs/commands.

lpm login
lpm whoami
lpm logout

lpm login opens a browser and stores the resulting LPM.dev Registry session in the operating system keychain, with an encrypted file fallback when the keychain is unavailable. lpm whoami shows the active account and plan.

By default, lpm logout clears the stored local session and asks LPM.dev Registry to revoke browser pairings associated with it. It does not revoke the current Registry token.

Use --revoke when the current token should also stop working server-side:

lpm logout --revoke

Token revocation and browser unpairing are best-effort, but the local session is cleared even if either network request fails.

Rotate an active token without signing out:

lpm token-rotate

See LPM CLI authentication and token rotation.

Connect npm-Compatible Tools

LPM CLI can use its stored session directly. Generate a project .npmrc when npm, pnpm, yarn, or another npm-compatible tool also needs access to @lpm.dev/*.

For local development:

lpm setup local
lpm setup local --days 7

This creates a read-only token, writes the scoped Registry configuration, and adds .npmrc to .gitignore.

For CI:

lpm setup ci npmrc
lpm setup ci npmrc --oidc
lpm setup ci github-actions
lpm setup ci gitlab

lpm setup ci npmrc writes project Registry configuration. The platform targets print starter CI workflows with LPM.dev Registry OIDC wiring; they do not write .npmrc.

See CLI Configuration and the canonical lpm setup reference.

Publish and Install Packages

lpm publish
lpm install @lpm.dev/acme.private-utils

lpm publish targets LPM.dev Registry by default. The Registry creates a private version first and applies the package's configured publication and distribution workflow.

lpm install is registry-aware. An @lpm.dev/* identifier goes to LPM.dev Registry, while public npm names and .npmrc scopes use their own registries.

lpm uninstall @lpm.dev/acme.private-utils

Use lpm uninstall to remove a dependency. lpm remove has a different purpose: it reverses source delivery performed by lpm add.

For source-delivered packages:

lpm add @lpm.dev/acme.login-form
lpm remove @lpm.dev/acme.login-form

See the LPM CLI references for lpm publish, lpm install, lpm uninstall, lpm add, and lpm remove.

Find Package Information

lpm search @lpm.dev/design
lpm info @lpm.dev/acme.design-system
lpm quality @lpm.dev/acme.design-system

Prefix a search with @lpm.dev/ to search the LPM.dev Registry catalogue. Other searches follow the project's normal .npmrc routing, including npm and private registries.

lpm info returns published package metadata. lpm quality shows the quality report associated with a Registry version.

See lpm search, lpm info, and lpm quality.

Pool and Marketplace Access

lpm pool

Authors use lpm pool to view current-period Pool download weighting and estimated earnings. Distribution changes and Marketplace purchases happen on lpm.dev; after access is granted, consumers install the package normally with lpm install.

See Pool, Marketplace, and the lpm pool reference.

Environments

lpm env set DATABASE_URL=postgres://...
lpm env push
lpm env pull

Local environment encryption is part of LPM CLI. push and pull add encrypted cloud sync through LPM.dev Registry. Organization sharing, platform delivery, and CI OIDC build on the same command family.

See Environments for the hosted service and the LPM CLI environment reference for every command and flag.

Tunnels

lpm dev --tunnel
lpm tunnel 3000
lpm tunnel 3000 acme-api.lpm.llc

Use lpm dev --tunnel to start a development server and tunnel together, or pass the port of an existing local service to lpm tunnel. A stable domain must be claimed before use.

See Tunnels for the hosted service and the LPM CLI tunnel reference for command details.

Swift Package Registry

lpm swift-registry
lpm install @lpm.dev/acme.swift-logger

lpm swift-registry configures Swift Package Manager authentication and signing trust for LPM.dev Registry. Run it for a Swift project before resolving Registry dependencies.

See Swift Package Registry and the lpm swift-registry reference.

Agent Skills and MCP

lpm skills list
lpm skills install
lpm mcp

Packages can publish Agent Skills alongside their code. LPM CLI can install and manage those skills, while lpm mcp exposes supported package workflows to MCP clients.

See Agent Skills, MCP Server, and the LPM CLI skills reference.

Complete CLI Reference

LPM CLI also provides npm-compatible package management, workspaces, lockfiles, security tools, a development server, task and test runners, local HTTPS, dependency graphs, plugins, and other local tooling.

Those features are documented at cli.lpm.dev, with a flat overview at cli.lpm.dev/docs/commands.