CLI reference

pylon --help        # full command list
pylon <cmd> --help  # per-command flags

curl -fsSL https://www.pylonsync.com/install.sh | bash

pylon login        # device-authorization flow: prints a login code, opens
                   # www.pylonsync.com/cli, and polls until you type + approve
                   # that code in the browser. No token paste.

pylon login --token <token>        # non-interactive: pass a token directly
pylon login --token-stdin          # read the token from stdin (CI / pipes)
                                   # (PYLON_CLI_TOKEN=… also works)

pylon login --code XXXX-XXXX
                   # agent-handoff path: redeems a one-time code minted by
                   # the dashboard's "Hand off to your coding agent" card.
                   # See /operations/agent-handoff.

pylon logout       # delete ~/.config/pylon/credentials.json

pylon projects list                # all projects you can see
pylon projects create my-app       # create + provision a project, set it as context
pylon projects use my-app          # writes .pylon/project + adds to .gitignore
pylon projects current             # what's the current context?
pylon projects use ""              # clear the context

pylon projects create my-app                       # SQLite, region iad, waits until live
pylon projects create my-app --name "My App"       # display name (defaults to the slug)
pylon projects create my-app --org acme            # required only if you're in multiple orgs
pylon projects create my-app --db postgres         # managed Postgres instead of SQLite
pylon projects create my-app --region ord          # Fly region
pylon projects create my-app --no-wait             # return immediately; check with `pylon status`

pylon test                         # run *.test.ts / *.test.tsx under tests/ (or functions/)
pylon test credits                 # only files whose path contains "credits"
pylon test --json                  # machine-readable summary
pylon test:security                # adversarial auth/policy probe vs a running app
pylon test:security --target https://api.example.com --json

pylon deploy                       # default → Pylon Cloud (packages local
                                   # source, uploads via the cli-tokens flow)

pylon deploy --target docker       # generate Dockerfile to ./deploy/
pylon deploy --target fly          #            Dockerfile + fly.toml
pylon deploy --target compose      #            docker-compose.yml + Dockerfile
pylon deploy --target workers      #            wrangler.toml (experimental)
pylon deploy --target systemd      #            systemd unit file
pylon deploy --target manifest     #            just manifest + client bindings

pylon secrets list                 # keys + last-rotated dates (values never leave the cloud)
pylon secrets set STRIPE_KEY=sk_…  # one-liner
pylon secrets set OPENAI_KEY       # prompt for value on stdin
pylon secrets rm STRIPE_KEY
pylon secrets import .env          # bulk import from a dotenv file
pylon secrets import .env --replace  # allow overwriting existing keys

pylon logs tail                    # 2s-polling tail of the project's request log,
                                   # Ctrl-C to stop. Pipe to grep/jq for filtering.

pylon logs tail --json | jq 'select(.status >= 500)'
                                   # all 5xx in real time

pylon db list                      # snapshot history
pylon db backup                    # take a fresh snapshot
pylon db restore <backup-id>       # restore from one

pylon data entities                # every entity in the deployed schema
pylon data list Order              # first 50 rows
pylon data get Order ord_9f2a      # single row, pretty-printed JSON

pylon domains list                 # custom hostnames + provisioning status
pylon domains add api.example.com  # adds row; prints the CNAME target
pylon domains verify api.example.com   # checks DNS + cert provisioning
pylon domains rm api.example.com

pylon deployments list             # 20 most recent
pylon deployments rollback <id>    # promote a previous deployment back to current

pylon members list                                       # everyone in the project's org
pylon members invite [email protected] admin          # invite with role
pylon members invite [email protected]                # defaults to member

pylon status                       # uptime, requests, error rate, jobs, WS/SSE clients
pylon status --json                # structured output for monitoring scripts

pylon jobs                         # 50 most recent jobs: name, status, tries, start, first error line
pylon jobs failed                  # only failed jobs
pylon jobs dead                    # the dead-letter queue
pylon jobs stats                   # pending / running / completed / failed / dead counts
pylon jobs get <id>                # one job with the full error text
pylon jobs --status retrying --queue mail --limit 200

pylon projects list --json | jq -r '.projects[].slug'

# fail CI on any project not in 'running' status
pylon status --json | jq -e '.status == "running"'

# nightly backup of every project you can see
pylon projects list --json | jq -r '.projects[].slug' | \
  xargs -I{} pylon db backup --project {}