Developers
Open app

Build & deploy

The acira CLI

The acira command-line tool lets you pull a site to your machine, edit it in any editor, preview it locally, and publish it back. It's the developer's path into the platform — the same projects the AI agent builds, on your disk, under your version control.

Install

# macOS / Linux
curl -fsSL https://cli.acira.ai/install.sh | sh

# Windows (PowerShell)
irm https://cli.acira.ai/install.ps1 | iex

The installer verifies the release signature before installing. Run acira upgrade to update to the latest signed release at any time.

Authenticate

Create an API key in the app under Settings → API Keys, then:

acira auth      # save and validate your key
acira whoami    # show who you're signed in as

Your key is scoped to your account and only reaches sites you already have access to. In CI, set ACIRA_API_KEY in the environment instead of running acira auth interactively — there's no key flag, so secrets stay out of your shell history.

The edit loop

acira pull my-site      # download the site to ./my-site
acira preview           # run it locally with live reload
# ...edit files...
acira lint              # validate locally
acira publish -m "..."  # take it live
acira status            # see local changes and whether the live site moved on

Pulling into an existing project does a three-way sync so you can pull the latest live version and keep your local edits.

Command reference

Command What it does
auth, whoami, list Sign in, show identity, list accessible sites
init Write the AGENTS.md guide for AI editors at your workspace root
create <name> Create a new site and scaffold it locally
pull <site> [dir] Download a site (three-way sync into an existing project)
preview Local dev server with live reload and the real runtime
status Local changes vs. the pulled version, and staleness
lint Validate templates, schemas, and logic locally
publish -m "<msg>" Publish the site live
logs Recent production console output and errors
deployments Deployment history
rollback <id> Re-publish a previous deployment
language List the site's languages; add/set/rm to change them
db <op> <table> Manage runtime database rows (query/get/create/update/delete/approve/restore/export)
backup <op> Point-in-time data recovery (bookmark/restore/undo/list)
upgrade Update the CLI to the latest signed release

Add --json to most commands for machine-readable output.

Good to know

  • Generated filesassets/styles.css and assets/scripts.js are produced by the platform on every publish. Don't hand-edit them.
  • Publishing runs checks — see Publishing & safety for the gates that run when you publish.
  • AI editors — run acira init so Claude Code, Cursor, and others understand the platform.
  • Hand-authored languages are CLI-onlyacira language add <code> --no-translate adds a language you translate yourself, which the app doesn't offer. See Internationalization.

Previous

Prompting the agent

Next

AI editors & AGENTS.md