Looking for every command, subcommand, and flag? See the complete Command Reference.
Quickstart
1
Install the CLI
2
Authenticate
3
Get a sandbox
4
Pull your code
.xs files.Commands at a glance
Auth and profiles
Login, contexts, and tokens.
Sandbox
Your personal dev environment.
Workspace
Git-friendly pull and push.
Branch
Labels, promotion, and live.
Function
Edit a single function fast.
Knowledge
Read agent knowledge and skills.
Release
Snapshots and deploys.
Tenant
Isolated multi-tenant deploys.
Testing
Unit and workflow tests in CI.
Hosting and platform
Frontends, platform, and updates.
Auth and profiles
Profiles store credentials and the active workspace + branch. Keep one per environment (prod / staging / dev) and switch with-p.
Full reference: Profiles →
Sandbox
A singleton dev environment per user, auto-provisioned on first call — the fastest path fromauth to shipping XanoScript.
Full reference: Sandbox →
Workspace
Canonical pull/push for shared and production workspaces. Splits the multidoc into a folder tree your version control will love.
Full reference: Push & pull →
Branch
v1 always exists and can’t be renamed or deleted. The live branch serves production traffic — set_live swaps it instantly.
Full reference: Workspaces & branches →
Function
Skip the full pull when you only need to tweak one function.edit with no flags fetches and opens it directly in $EDITOR.
Full reference: Function commands →
Knowledge
Read the agent knowledge and skills that shape how AI agents build in a workspace. Both commands are read-only and print plain-text markdown by default.
Full reference: Knowledge commands →
Release
Releases are named, versioned snapshots of a branch. Deploy them to tenants, export them to a file, or move them between workspaces.
Full reference: Releases →
Tenant
Each tenant has its own database, env vars, license, and backups. Direct push is blocked — deploy through a release or iterate in a sandbox.
Full reference: Tenants →
Testing
Tests are authored in the dashboard; the CLI runs them. Use-o json for machine-readable results in pipelines.
Full reference: Workflow tests →
Static hosting, platform, and maintenance
Ship the SPA next to the API, pin the runtime version, and keep the CLI itself current.
Full reference: Static hosting →
Power-user tips
Global flags
Available on any command:
-p <name>— swap profile-c <path>— alternate credentials file-v— verbose HTTP-o <fmt>— output format (summary/json/xs)
Override with env vars
Sandbox vs. workspace
Sandbox for personal experiments and AI-generated code. Workspace for shared/production code and CI. Same multidoc layout — workflows translate 1:1.
Always dry-run first
--sync --delete only when you want a true mirror. The default mode is partial (changed-only).Binding is by guid, not path
Objects bind by the
guid line inside each .xs file — not by folder or ID. There is no .xano/objects.json or manifest. A fresh pull regenerates each file with its correct guid, so pushing updates in place instead of duplicating.How objects are identified →Glob filters
-i includes and -e excludes — both repeatable, both glob.Atomic by default
Pushes wrap in a DB transaction and write server-assigned GUIDs back to local files. Disable only when needed with
--no-transaction or --no-guids.Edit a function in $EDITOR
Reuse the token
CI/CD recipe
Branches as environments
v1 is reserved.Include data on pull/push
Add data alongside code:
--records— include table rows--env— include env vars--draft— include drafts
pull --env --records --draft.Tenant push is blocked
Go deeper
Command Reference
Every command, subcommand, and flag.
Get Started
Install, authenticate, and pull your first code.
Team workflows
Branching, releases, and promotion across a team.
Push & pull
How the multidoc maps to a local folder tree.