Skip to main content
aeo agent context
aeo strategy show
aeo visibility show
aeo metrics overview
Write the article in your own environment. Then import: 
aeo content import \
  --title "The runner's guide to no-white-cast sunscreen sticks" \
  --body-file ./draft.md
content import does not accept --status; a full imported draft is created in review state. Review: 
aeo content review <content_id>
Apply edits: 
aeo content update <content_id> --body-file ./draft.revised.md
Preview: 
aeo content preview <content_id>
content preview creates or reuses a public, unauthenticated preview URL. Avoid pasting private preview URLs into public logs, tickets, or chat transcripts. Deploy after explicit user approval: 
aeo content deploy <content_id>
Deploy requires approved status: 
aeo content update <content_id> --status approved
aeo content deploy <content_id>

​
Server-side generation

Use this only when the user asks Aeolo to generate the article: 
aeo content generate --prompt "best sunscreen stick for runners"
aeo content jobs
Server-side generation creates a background writing job and consumes credits. The current CLI does not support --wait for content generation; use aeo content jobs, then aeo content list or aeo content get <content_id> after completion. For coding agents, direct writing plus content import is usually better because the agent can use its own local drafting loop.

​
Updating existing content

Use content update for concrete revisions only: 
aeo content update <content_id> --title "New title"
aeo content update <content_id> --status approved
aeo content update <content_id> --body-file ./article.md
Do not rewrite user-owned published content without approval.