Ae Agent

ae-agent

CRITICAL — Before running any `ae-cli agent +<command>` command, you MUST first read the corresponding `references/<command>.md`. The reference filename equals the command name without the leading +, for example +add-mcp -> references/add-mcp.md. CRITICAL — Before running hierarchical approval commands, read the matching resource reference: `approval-type.md`, `approval-request.md`, `approval-task.md`, or `approval-effect.md`. CRITICAL — Before running `agent bundle`, `agent share`, or `agent submission` commands, read `references/agent-distribution.md`. Agent and Skill share IDs are not interchangeable. CRITICAL — Never guess record IDs (Agent / automation / model / MCP / Skill / submission / share / attachment). Always use the appropriate +list-* command to discover real IDs first. *CRITICAL — Legacy Agent CRUD uses `/api/sandbox/agent/; Agent distribution and generic approvals use CLI-token-only /api/cli/agent/v1/` and `/api/cli/approval/v1/. ae-cli memory uses /api/cli/memory/v1/`.* Do not use Web session or sandbox credentials for CLI-token endpoints.

AE CLI (ae-cli) agent platform resource commands are invoked through:

ae-cli agent +<command> [options]

Agent resource commands live under the agent service. Quick help:

ae-cli agent --help
ae-cli agent +list-agents --help
ae-cli agent +create-automation --help
ae-cli agent approval-request --help

User memory commands live under the memory service:

ae-cli memory +<command> [options]

Global AE CLI Rules

• Use this skill for Agent platform resource management: Agents, generic approvals, archived conversations, automations, models, MCP servers, Skills, attachments, the MCP/Skill market, Agent and Skill approval/share flows, and user memories.
• Read operations (risk: read) can run directly once required IDs are known.
• Write operations (risk: write) can run directly once required IDs and references are verified.
• High-risk write operations (risk: high-risk-write) require explicit user authorization. Pass --yes only after the user confirms.
• Prefer --dry-run before high-risk write operations to inspect the request shape without executing.
• Local-Agent runtime memory +mark-used is silent internal usage accounting after an answer actually uses memory.
• Personal and company scope resources can be created/updated/deleted; company scope requires root/agent_admin role; system resources are read-only (exception: root users can approve/reject submissions and set company-scope meta).
• Toggle operations on company/system resources only affect the current user's preference, not the global state.
• Never invent record IDs. Discover them with +list-* commands or accept them from the user.
• JSON flags must be valid JSON strings, usually wrapped in single quotes in shell.

Global Parameters

Output and Errors

• Successful commands return machine-readable JSON by default. Use --format table when a table is easier to scan. Envelope may include optional _notice.host_compat.
• Failed commands return { "ok": false, "error": { "type": "...", "message": "...", "hint": "..." } } and exit non-zero.
• CRITICAL — Host compat (do this first): After each ae-cli run, check stderr and _notice.host_compat. If either is present, open the user reply with a short ⚠️ version warning and quote the `npm i -g` / `npx skills add` (or update-cluster) lines verbatim, then present the business result. Soft tip; ok: true can still carry the notice.

When to Use

Use ae-agent for all Agent platform resource work:

• Agents, conversations & automations: manage Agents, share immutable Agent snapshots, submit Agents for company publication, preview approval snapshots, find/restore archived conversations, and manage scheduled Agent automations.
• Models: list, add, delete, toggle custom models.
• MCP servers: list, add, delete, toggle MCP servers; browse the MCP market; set market meta.
• Approvals: discover versioned approval types, submit/query/cancel approval requests, and query/approve/reject approval tasks.
• Skills: list, add, delete, toggle Skills; browse the Skill market; set market meta; copy system/company Skills to personal; use legacy company-publish approval commands during the compatibility period; share/accept/reject peer-to-peer Skills.
• Attachments: list, upload, soft-delete sandbox files in the attachment library.
• User Memory: recall, account for, create, update, extract, organize, preview, and initialize long-term user memories through the memory domain.

If the user's intent is data analysis, audience management, metadata governance, TeamRuns, or knowledge bases, switch to ae-analysis / ae-engage / ae-dataops / ae-team / ae-kb.

Tool Groups (89 commands)

Agents (6)

• +list-agents (doc) — list Agents visible to current user (personal/company/system)
• +create-agent (doc) — create a new Agent (personal/company scope; company requires root/agent_admin; name/description/instructions/model/mcp-ids/skill-ids)
• +update-agent (doc) — update an Agent's name/description/instructions/model/mcp-ids/skill-ids/enabled
• +del-agent (doc) — soft-delete a personal/company Agent (company requires root/agent_admin; system Agents cannot be deleted)
• +get-agent (doc) — get a single Agent's detail
• +get-agent-context (doc) — resolve instructions and dependency discovery for local execution; use ae-use-agent for the workflow

Agent Distribution (7)

Read the complete share and company-publication workflow first.

• bundle preview — check current dependencies without creating a share or submission
• share recipients — find eligible same-company recipients, including as an ordinary member
• share create — send an immutable personal Agent snapshot to selected recipients
• share list — list received/sent shares, pagination, versions, and allowed actions
• share accept — create or strictly reuse personal Agent and bundled Skill copies
• share reject — reject a received share without creating assets
• submission preview — read the authorized immutable approval snapshot, including after rejection

Company submission, cancellation, approval, rejection, and execution retry reuse the Generic Approval Workflow below with agent.publish@1.

Archived Conversations (2)

• +find-archived-conversations (doc) — find archived conversations for the current/specified Agent or explicitly across all Agents, with user-facing timestamps converted by --time-zone