The CLI for the agent cloud.
One small binary runs coding agents, deploys apps and sites, routes 100+ models, manages repos and CI, rents machines, and reaches every endpoint with app api. Everything below is real output.
macOS, Linux, and Windows builds — or go install github.com/app-nz/app-cli/cmd/app@latest. Source at /repos/leepenkman/app-cli.
Real recorded session, sped up: a cloud agent writes the game, app apps deploy ships it.Play the result →
1 — Sign in
Create a key at app.nz/account, then app login --api-key pk_live_... Every command uses the same key as the API and web app.
2 — Build with an agent
app agent run hands a plain-English task to a cloud coding agent that branches, codes, tests, and opens a PR on your repo.
3 — Deploy
app apps deploy packages the directory, runs the build server-side, and serves it at <name>.app.nz with HTTPS. No DNS, no YAML beyond one file.
Quick copy for any LLM
Give an agent a complete, safer brief.
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
From a good brief to the right runtime.
Read-only sessions recorded from the real CLI and live public catalog—safe to replay, copy, and adapt.
Create a bounded brief, inspect available agent providers, then choose a maintained task prompt.
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 with zero config), uploads a source tarball, runs your build on the server, and publishes to <name>.app.nz. Server runtimes get a managed process, injected PORT, env vars per deploy, 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: 3000Scriptable by design
Every command takes --json for machine-readable output, reads APP_API_KEY / APP_BASE_URL from the environment, and exits non-zero on failure — drop it straight into CI, cron, or an agent's toolbox.
Coming from GitHub's CLI? app parity prints the gh command-coverage manifest — repo, issue, pr, release, secret, ruleset and friends behave the way your fingers expect.
Command reference
Auth & account
Apps hosting
Heroku-style deploys driven by appnz.yaml — static buckets or server runtimes at <slug>.app.nz.
Static sites
The fastest path 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 · machine-readable guide for agents: /llms-full.txt