Skip to main content
The aci command-line interface is the developer entrypoint for ACI sites. It validates the frontend contract, compiles content, runs framework development servers, syncs content, and calls branch and DAM APIs.

Installation

Design partner starters install @gradial/aci as a project dependency. Use the starter scripts first:
You can also invoke the local CLI directly:

Global Flags

Commands

Local Development

aci doctor

Checks local site configuration and tooling.
It checks:
  • .aci.yaml is discovered and valid
  • version, siteId, and framework are valid
  • Component registry, layout registry, and renderer entry exist
  • The renderer exports a GradialRenderer
  • Node.js and npm are available
  • Framework-specific requirements, such as Next.js catch-all routes, are present
  • .aci/registry.json can be compiled and loaded

aci build

Compiles content and builds the configured framework site.
Flags: Common starter scripts:

aci dev

Runs the configured framework development server with ACI content environment variables.
Flags: aci dev compiles registries if needed, sets ACI_CONTENT_ROOT, starts a local /aci-dev websocket for content refresh notifications, and then runs the framework’s npm run dev.

Content Commands

aci content pull

Pulls content from the hosted API or directly from S3 into a local content directory.
Flags:

aci content clone

Clones a path-scoped API content workspace.
Use this when an agent or developer should work on a focused subset of content files. --path is required and can be repeated.

aci content push

Pushes local content workspace changes through the API.

Branch Commands

Branch commands call the ACI API. They default to http://localhost:8080 and token dev-user, or you can pass --api-url and --token.

aci branch list

aci branch create

aci branch get

aci branch changes

Applies explicit JSON changes to a branch.

aci branch patch

Applies an RFC 6902 JSON patch to one content file.
Patches /config/site.json to point at a code artifact.

aci branch rebase

aci branch land

Squash-lands a branch into the target branch.

DAM Commands

DAM commands call the ACI API and use the signed upload/download flow.

aci dam upload

Uploads a new DAM asset binary.
Metadata is edited through commit-engine files; the upload command only handles binaries.

aci dam upload-version

Uploads a new immutable binary version for an existing asset.

aci dam download

Downloads a DAM asset original.

Environment Variables

Typical Workflows

Local Starter Development

Validate Before Commit

API Content Workspace


Next: Quickstart →