Last updated: 2026-09-06
orca agents manages agent profiles: the runtime, model, prompt, tools, skills, and MCP servers that define an agent. Agents are created and updated from a YAML or JSON agent document.
Every subcommand accepts the global flags. Subcommands that take an optional [name] open an interactive picker when the name is omitted in a terminal; in a pipe or script the name is required (exit code 2).
orca agents list
published column from a second request; if that request fails the column shows ? and the listing still succeeds.
name, runtime, model, published.
orca agents get
--json the full profile object is printed; the plain view prints name, runtime, model, and skills.
orca agents changes
created, updated, deleted), the fields that changed, and the redacted before and after snapshots (in --json output only).
The server returns up to 200 entries;
--limit trims client-side.
orca agents create
Unknown keys in the document produce warnings on stderr but do not block the create unless
--strict is set.
orca agents update
name field in the document; pass a different [name] to rename an existing agent (the old name is the positional, the new name is in the file).
orca agents delete
--yes is required or the command refuses (exit code 2).
orca agents publish
The
--json output is the published-agent record, including publicUrl. After publishing, issue a chat key with orca agents keys create <name>.
orca agents unpublish
orca agents keys
Chat keys authenticate callers of a published agent through the gateway. They are separate from tenant API keys, which authenticate the CLI itself.orca agents keys list
active, expires <time>, or revoked).
orca agents keys create
--json the full issued-key record is printed.
orca agents keys revoke
Verified against orca-cli
cli-v0.5.0.