Skip to main content
Almost every command accepts a global --json flag that emits a structured envelope ({ "success": true, "data": {...} }) to stdout for scripting, piping, and coding agents. Run aui <command> --help to see the full, non-interactive option list for any command.

Quick Reference


Authentication & Session

Authenticate with the AUI platform using the --environment option. It opens the browser to sign you in to the chosen environment (production is the default):
Clear the local session and stored credentials.
Display current session info, linked agent, and a summary of local project files. Renders a human-readable view by default; pass --json for the structured envelope.
Show or switch the active environment.
The active environment is stored in ~/.aui/environment.
Re-scope your local session (organization, account, and token) to match this project’s .auirc. Alias: aui update-session.
aui login issues a token scoped to your default organization. If you imported an agent that lives in a different org, push / pull / apollo calls return 403 or 404 until the session is re-scoped. This command fixes that — and the CLI runs the same reconciliation automatically before most commands. It’s a no-op (zero network calls) when already in sync.

Accounts & Agents

Manage accounts (projects). Alias: aui accounts.
Manage agents and versions — list, create, switch, import, delete. Alias: aui agents.
Agent creation is always bundle-mode: one call provisions everything server-side (network → agent → first version → publish → activate). After creating, the CLI auto-imports the agent into a ./<agent-name> folder and drops you into an interactive subshell — run exit to return.
Quick table view of all agents in the current account. Alias: aui ls.
Download an agent’s configuration as local .aui.json files. Alias: aui import.
Downloads general settings, parameters, entities, integrations, tools, and rules; fetches JSON schemas for editor autocomplete; generates a GUIDE.md; and (by default) scaffolds coding-agent skills.
Pull the latest agent files from the backend, overwriting local .aui.json files.

Push, Diff & Validate

Upload local changes to the AUI backend as a new revision on your draft version. Changes are detected via git diff against the last push baseline.
Compare two agent configurations, or show changes since the last import/push.
Validate .aui.json files against domain schemas (*.dschema.json).
Performs JSON syntax checking, required-field validation, and cross-reference integrity (e.g. tools referencing valid integrations).
Fetch the latest domain schemas (*.dschema.json) from the backend for local validation and editor autocomplete.
Reset the project to HEAD, discarding all local changes. Uses git under the hood.

Runtime Messaging — Apollo

The aui apollo commands wrap the Apollo runtime endpoints. They default to JSON output (built for tooling and coding agents) — pass --pretty for the human terminal view. send-message and rerun validate and forward your local .aui.json files, so replies reflect your latest edits.
Start a new conversation thread with an agent. Alias: create-task.
Returns a task ID you pass to the other commands as --task-id.
Send a message to an agent and get a reply. Forwards your local agent files by default so the reply reflects your latest edits.
The reply always includes the trace (trace_info). The id it returns is the interaction id for rerun / trace --interaction-id.
Regenerate a thread from a given interaction with edited text, then replay. Forwards your local agent files by default.
Fetch interaction traces for a conversation thread. Saves traces to traces/trace_{sequence}.json and prints a compact summary by default.

Version Management

Manage the agent version lifecycle. The agent and target version default to your project’s .auirc.
Version states:
  • Draft — editable, not live
  • Published — locked, can be activated
  • Active — the live version users talk to
  • Archived — preserved but inactive
Browse, inspect, and diff version snapshots — the complete agent configuration captured at a point in time.

Integrations

Wire up external capabilities as manual MCP integrations (your own MCP server) or native Composio integrations (from the toolkit directory). The discovery, create, and test subcommands are fully non-interactive with --json support. Alias: aui integrations.
Use --full for a fully non-interactive create (missing required flags fail instead of prompting).
OAuth client-credentials and Composio BYO-auth flags (--oauth-*, --composio-*) are also supported — run aui integration create --help for the complete list.
Both test commands always emit JSON and are fully non-interactive.
By default integration test sends a bundle_mapping so the response also returns mapped_entities — a preview of the entities the runtime would extract. Pass --raw for a plain endpoint call with no mapping.

Mock DB

aui mockdb provisions a per-agent test database so you can develop and test tools against realistic data without touching production systems. All subcommands emit JSON.
Seed rows accept relative date tokens like now-30d. Endpoint kinds are read / insert / update / delete; writes via execute require a --session (copy-on-write overlay). Create parent collections before children so foreign keys resolve.

Agent Configuration

Manage RAG (Retrieval-Augmented Generation) knowledge bases and files.
The RAG API key is stored securely at ~/.aui/kbm-key (file mode 600).
Store and manage secrets referenced by your integrations. Secrets are scoped and never printed back in full.
Evaluation scenarios and scores. Run these from inside an agent project directory (they read agent_management_id / version_id / version_tag from .auirc) and are fully non-interactive.
Local layout: scenarios/scenarios.aui.json, scenarios/scenarios-scores.aui.json, and scenarios/intent/ (raw intent files, docs, sample data). Scenario generation is skill-driven — the coding agent fills in scenarios from the intent files.

Tools

Launch a web-based chat playground on localhost to test your agent in the browser.
Update aui-agent-builder to the latest version published on npm.
Show the HTTP requests made by the last command, rendered as reproducible curl commands. Useful for debugging and for understanding exactly what the CLI sent.
Beta
Report a CLI or agent issue, a learning, or a suggestion back to AUI. Coding agents driving the CLI are expected to use this to surface problems.