app cli

The app.nz CLI.

One binary runs coding agents, deploys apps and sites, routes 100+ models, manages repos and CI, rents machines, and calls every endpoint with app api. Everything below is real output.

macOS, Linux, and Windows builds, or go install github.com/lee101/app/cmd/app@latest. Source at /repos/leepenkman/app-cli.

app: build and ship a game

Loading recording…

Recorded session, sped up: a cloud agent writes the game, app apps deploy ships it.Play the result →

1. Sign in

Run app login. App neocloud CLI, API, desktop cloud bridge, Git credentials, and MCP proxy all work together.

2. Build with an agent

app agent runs a coding agent in your terminal. app agent run sends the task to a cloud agent that branches, codes, tests, and opens a PR.

3. Deploy

app apps deploy packages the directory, runs the build server-side, and serves it at <name>.app.nz over HTTPS. No DNS, no extra YAML.

Quick copy for any LLM

Markdown briefs for agents.

Raw Markdown guide ↗

Read https://app.nz/llms-full.txt, especially “Launch a cloud coding agent”.

Use app.nz to complete this outcome: <describe the outcome>.

- Repository: <owner/repo>
- Constraints: preserve unrelated work; never expose secrets; ask before destructive or costly actions.
- Execution: choose an appropriate agent/model route, inspect existing instructions, implement the smallest coherent change, and run relevant tests.
- Visual changes: capture desktop and mobile evidence in VisualBench and inspect it.
- Return: summary, changed files, tests, remaining risks, and PR/deploy URL when created.

Also available offline as app guide agent and through the app.nz MCP server.

Recorded workflows

Agent and model workflows.

Read-only sessions recorded from the real CLI and the live public catalog.

app: brief and choose a coding agent

Loading recording…

Write a bounded brief, inspect the available agent providers, then pick a task prompt.

app: route models without rewriting your client

Loading recording…

Start with the router, then filter the live model catalog by provider and keep a fallback ready.

Hosting: one manifest, two runtimes

app apps deploy reads appnz.yaml (or deploys a bare directory as a static app), uploads a source tarball, builds on the server, and publishes to <name>.app.nz. Server runtimes get a managed process, injected PORT, per-deploy env vars, and app apps logs.

# appnz.yaml: one file describes the deploy
name: neon-snake
runtime: static     # or: server
output: .           # dir published to neon-snake.app.nz

# server runtimes add:
# build:
#   command: npm ci && npm run build
# run:
#   command: node server.js
#   port: 3000

Scripting and CI

Every command takes --json, reads APP_API_KEY / APP_BASE_URL from the environment, and exits non-zero on failure. Runs in CI, cron, or an agent's toolbox.

app parity prints the gh coverage manifest: repo, issue, pr, release, secret, and ruleset map to the gh commands.

Command reference

Auth & account

Apps hosting

Heroku-style deploys driven by appnz.yaml. Static buckets or server runtimes at <slug>.app.nz.

Static sites

For plain files: mirror a directory to a hosted site.

Coding agents

Models & chat

Repos, PRs & CI

GitHub parity: repo, issue, pr, release, label, secret, ruleset, gist. Check coverage with app parity.

Addons

Managed services attached to a repo or deploy. Env vars (DATABASE_URL, GOBED_SEARCH_URL, APP_ADDON_*) injected into every runtime.

Machines & data

Billing & escape hatch

Full API behind every command: /docs · agent guide: /llms-full.txt