CLI vs SDK
CLI (
sylphx) is for operators and agents on the Management plane. SDK (@sylphx/sdk) is for app code. They are different products — see SDK installation.Quick install
macOS / Linux
curl -fsSL https://raw.githubusercontent.com/SylphxAI/platform/main/scripts/install-sylphx.sh | bash
sylphx doctor
sylphx loginMore channels (npm, Cargo, Homebrew): Install the CLI. How upgrades work: Update the CLI.
What you can do
Auth & context
login, doctor, org/project link, whoami
Deploy loop
deploy, status, logs, rollback, env, services
Platform resources
db, storage, domains, secrets, backups, flags
Agent / CI
JSON output, service tokens, candidates publish
Day-1
sylphx login
sylphx orgs list
sylphx context use --org-id org_…
sylphx projects list
sylphx link --project proj_… --org-id org_…
sylphx status
sylphx logs --tail 100CI / service tokens
export SYLPHX_TOKEN=svc_… — no interactive login. Prefer sylphx … --json for agents.Industry rules (short)
- One binary — channels only distribute; they do not fork behavior.
- Update the way you installed — npm → npm, brew → brew, curl → update or reinstall.
- No silent auto-update — upgrades are explicit commands only.
- No WASM CLI — the operator CLI is a native binary (not a browser isolate).