CLI Command Catalog

Complete command-line execution catalog for managing workspaces, local dev servers, cloud deployments, and authentication handshakes.

Published: 7/10/2026

Command Catalog Overview

The Aircada CLI exposes high-performance commands for scaffoldings, local live-reload dev sessions, and optimized cloud production releases.

1. air init

Initializes a brand new Aircada project structure in your current working directory.

bash

air init [flags]

Flags:

- -t, --type <PROJECT|PLUGIN>: Specify application layout to construct. If omitted, triggers an interactive prompt.

- -i, --id <projectId>: Define parent project identifier (required for PROJECT).

- -n, --name <name>: Define the plugin's global display name (required for PLUGIN).

- -d, --dev: Bootstraps in local internal development mode injecting appropriate environment variables.

Behind the Scenes: Builds base filesystem folders, generates TS boilerplates, installs dependencies, synchronizes cloud schemas via IntelSyncer, and registers the workspace with the Cloud directory.

2. air setup

Registers your local project structure with the Aircada Cloud directory.

bash

air setup

Behind the Scenes: Loads and validates air.config.json, dispatches a POST /pluginConfigCommand with the registration payload, and writes the cloud-generated appId back to your local config.

3. air login

Authenticates your terminal environment securely with the Aircada Cloud directory.

bash

air login

Behind the Scenes: Launches the secure loopback ephemeral server, opens a browser session to the web dashboard, securely transfers high-entropy session keys, encrypts credentials via AES-256-CBC, and stores them in the secure binary credentials lock file.

4. air logout

Removes local session state, logging you out completely.

bash

air logout

Behind the Scenes: Permanently deletes the local secure lock file (~/.aircada/credentials.lock).

5. air dev

Boots the local live-reload development server and connects to the interactive cloud Studio interface. For details, see CLI Development Server.

bash

air dev [flags]

Flags:

- -p, --port <port>: The port to bind the development server to (default: 9005).

- -d, --dir <directory>: Specify project root workspace directory (default: .).

6. air build

Bundles, compiles, and optimizes the local project for production deployment.

bash

air build [flags]

Flags:

- -d, --dir <directory>: Specify target project root directory (default: .).

- -o, --out <outputPath>: Custom output location for target compiled file (default: dist/application.js).

Behind the Scenes: Invokes an optimized esbuild runner configured with heavy tree-shaking, production minification, and CSS compilation.

7. air publish

Compiles your project and deploys a production version to the Aircada Cloud.

bash

air publish [flags]

Flags:

- -d, --dir <directory>: Specify project root directory (default: .).

- -v, --version <version>: Override version label (defaults to auto-incrementing package.json version).

- --dryRun: Runs compile and dry validation check but does not upload.

- --skipBuild: Uploads the current dist/application.js without running the compiler.

Behind the Scenes: Auto-increments patch versions, triggers optimized production bundlers, requests storage signed upload URLs, uploads bundles to Azure blob buckets, and finalizes cloud-side registry commits.

8. air transfer-urls

Optimizes heavy remote network assets in local datasets. Scans a CSV, uploads all parsed external image/media assets to Aircada cloud blob storage, and substitutes references with optimized media IDs.

bash

air transfer-urls <filename> [flags]

Behind the Scenes: Parses local CSV files, isolates external assets, uploads them to the Media Vault storage engine, and replaces raw links with cloud-native Media Item IDs, saving a sanitized CSV back to the disk.

9. air mcp

Launches the Aircada Unified Smart Gateway Model Context Protocol (MCP) Server in stdio communication mode. For details, see Model Context Protocol (MCP).

bash

air mcp

10. CLI Development Commands

Use these standard workspace commands if developing or contributing to the CLI codebase itself:

bash

# Install development dependencies
npm install

# Link to local development packages
npm run link-air

# Clear existing distribution compiles
npm run clean

# Run continuous compilation and template copying
npm run build

# Run project unit test suites
npm run test