> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aeolo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# CLI overview

> How to use aeo as a human or external-agent tool.

The `aeo` CLI is designed for both humans and coding agents. It returns Markdown or structured text that LLMs can read without scraping dashboard UI.

## Default external-agent loop

```txt theme={null}
Read context
  -> gather measurement and source evidence
  -> draft locally
  -> import draft
  -> review
  -> update
  -> preview or deploy after approval
```

That means the usual writing path is:

```bash theme={null}
aeo agent context
aeo visibility show
aeo strategy show
aeo content import --title "..." --body-file ./draft.md
aeo content review <content_id>
```

Use `aeo content generate` only when the user explicitly asks Aeolo to generate content server-side.

## Command families

| Family                                   | Purpose                                   |
| ---------------------------------------- | ----------------------------------------- |
| `auth`, `whoami`, `billing`              | Credentials and account state.            |
| `domain`, `agent`, `strategy`, `config`  | Brand setup and context.                  |
| `visibility`, `audit`, `metrics`         | Measurement and diagnostics.              |
| `content`                                | Article lifecycle.                        |
| `channel`, `post`                        | Publishing channels and social posts.     |
| `reference`, `video`, `image`, `product` | Reference analysis and media workflows.   |
| `drive`                                  | Read connected Google Drive source files. |

## Output formats

Most commands default to readable Markdown. Where supported, pass JSON flags if the command exposes them. MCP responses wrap the same command output in tool call content.