Start

For agents: Read llms.txt, create manifest.userland.json, add public/ files, add server/index.js only when dynamic routes are needed, then publish with a server-side CLI or API call using USERLAND_API_KEY or a saved CLI API key. The selected or default platform account owns the app.

Goal

Build a valid Userland app bundle and publish it to an immutable app origin.

Inputs

• App idea and expected user workflow.
• USERLAND_API_KEY in the local environment, or an API key saved by userland signup, userland login, or userland auth save-key.
• Optional platform account id for team, client, or agency workspaces.
• Optional examples from the public examples repo.

Outputs

• manifest.userland.json.
• Static files under public/.
• Optional server module at server/index.js.
• Published app_id, origin, release_id, and activation status.

Commands

npm install -g @userland.fun/cli
userland auth status
userland login
userland apps publish .
userland apps publish . --account "$ACCOUNT_ID"

Single-user flows can omit account selection. Use userland accounts list, userland accounts use "$ACCOUNT_ID", USERLAND_ACCOUNT_ID, or --account when the app should belong to a non-default account.

The CLI login flow opens the browser for device authorization and saves only an API key. Console signin uses email links. There is no platform password or platform password reset flow for launch auth.

Generated artifacts

• /llms.txt for compact agent context.
• /openapi.json for the control-plane API.
• /schemas/resource-manifest-v0.schema.json for manifest.userland.json.
• /types/runtime-context-v0.d.ts for server runtime code.

Do not put API keys, app secrets, or platform internals into app frontend code.