CLI

Use AIP CLI as the utility layer for agent development after you finish conceptual design in Guides.

When to Use CLI

• Validate access and environment health before coding: aip status.

• Operate resources without writing scripts: list, inspect, create, update.

• Run and debug agents interactively with rich streaming output.

• Export/import agents, tools, and MCPs for promotion workflows.

Placeholder Legend

• <ACCOUNT_NAME>: Named CLI account profile (for example prod, staging).

• <AGENT_REF>: Agent ID or unique agent name.

• <TOOL_REF>: Tool ID or unique tool name.

• <MCP_REF>: MCP ID or unique MCP name.

• <RUN_ID>: Run ID from transcript or history views.

• <EXPORT_FILE>: Output file path, for example agent.yaml.

CLI Learning Path

1. Start with the Lifecycle tutorial.

2. Continue with Use cases.

3. Learn core commands in Accounts, Status, and Agents.

4. Add capabilities with Tools, MCPs, and Models.

5. Capture output using Runs and Transcripts.

6. Promote config safely with MCP export/import workflow.

Interactive UX

• Open the palette with aip and use /accounts, /agents, /status, and /transcripts.

• After selecting an agent via /agents, use /runs and /schedules for remote debugging and automation.

• Workflow guide: Slash palette.

Command Reference

• Detailed flags and options: CLI Commands Reference.

• Legacy config format: CLI Legacy Config.