Skip to content

For AI Assistants

Where should an assistant start? If it has no access yet, start at Choose your setup. In the app, open Connect. If the assistant is already connected, read the guide for the operating path it uses. Running cai docs with no path prints this compatibility page as Markdown.

Use the CLI when the assistant works through a terminal. Use Remote MCP when its host connects through OAuth. Keep one operating path for the task.

  • Use the CLI explains account checks, workflow selection, local files, JSON results, and interrupted operations.
  • Use Remote MCP explains scopes, typed inputs, explicit workflow IDs, and existing executions.
  • Skills and updates helps you select and maintain the guidance your assistant uses.
  • Assistant security explains credentials, approvals, and the in-product builder’s access.

For a first build, create Support helper or Invoice intake. Look up exact command and tool inputs in the CLI reference or MCP tool reference.

To discover pages, use llms.txt. llms-full.txt no longer includes the two generated catalogs, reference/cli and reference/mcp-tools. They are excluded to keep the file small. Each one is still available as its own .md page: /reference/cli.md and /reference/mcp-tools.md.