Sume CLI commands: a reference for account, jobs, assets, and skills
The Sume CLI commands beyond generation: login and account, health and doctor checks, schema discovery, jobs, assets, batch helpers, skills, and aliases.
The Sume CLI (sume) covers account verification, catalog discovery, jobs, input assets, Avatar 1.0 and Avatar Video 1.0, bundled agent skills, schema discovery, and local diagnostics. The Avatar commands are the only generation submit path; the others handle accounts, reads, job recovery, assets, and setup, and sume tools schema <name> --json prints exact schemas at runtime.
The list comes from the CLI Command reference and Jobs and media inputs pages, read on 2026-09-26. The docs say the CLI still works but is not part of the primary path today. Avatar generation from the terminal is covered in the CLI tutorial.
Which commands does the Sume CLI have?
Every command below starts with sume. Add --json for stable machine-readable output, and --agent to redact URL-like and sensitive account or workspace fields where the CLI supports it.
| Group | Commands | What the docs say |
|---|---|---|
| Auth | login, login --no-browser, logout, auth status, auth setup --api-key | --no-browser prints the approval URL for remote or headless terminals. |
| Account | me, account get, balance, usage get --limit 20 | me and account get both read account context for the configured key. |
| Catalog and health | catalog list, health, health service, health v1 | Read commands. |
| Local diagnostics | doctor --agent --json, version, update --check | doctor inspects local readiness without calling the API. update --check modifies no local files. |
| Schemas | tools list --json, tools schema <name> --json | Discover exact schemas at runtime. |
| Jobs | jobs list, get, status, events, result, watch, download, cancel | watch polls until terminal or timeout. download --output-dir saves completed media. cancel needs --confirm-submit. |
| Assets | assets list, get, create --source-url, download-url, download | Write paths are gated. See the status note below. |
| Avatars | avatars list, get, create, batch; avatar-videos list, get, create, batch | The only generation submit commands. create needs --confirm-paid. |
| Skills | skills list, install <name>, update, remove <name>, export <name> | Installs into .agents/skills or .claude/skills. |
How do I find a command's exact flags?
Ask the CLI. sume tools list --json and sume tools schema <name> --json discover exact schemas at runtime; the docs use jobs.result, assets.create, avatars.create, and avatar-videos.create as schema names. The docs recommend validating a payload with a read-only schema command before any write or paid step.
The batch helpers, sume avatars batch and sume avatar-videos batch, run plan, create, watch, and result steps against local state files; inspect them with sume avatars batch --help. For skills, sume skills export sume lets you review the packaged skill's source files before a custom install.
Which commands need a confirmation flag?
Write commands require explicit confirmation: --confirm-submit for non-paid writes such as sume jobs cancel <job_id> and asset registration, and --confirm-paid for sume avatars create and sume avatar-videos create, which can reserve or spend credits. The CLI tutorial shows the agent-safe loop around these gates.
What is the status of the asset commands?
The asset commands list, register, and download first-party input assets, for workflows that need asset ids instead of bare public URLs. The CLI wraps the Developer API, whose /v1/assets routes are implemented but hidden from the public OpenAPI document; the API reference says not to treat them as documented public contract until they reappear there. Both pages give the same advice: prefer public HTTPS media URLs in generation requests.
Which commands are aliases, and which do not exist?
sume models list is a deprecated alias for sume catalog list, and sume me reads the same account context as sume account get.
There is no sume image, sume video, or sume music subcommand. The CLI docs route that work to Image 1.0, Video 1.0, and Music 1.0 over HTTP. Image 1.0 and Video 1.0 are retiring soon, so new integrations call POST /v1/images or POST /v1/videos with sume/auto, as the migration guide explains; Music 1.0 is retiring gradually in favor of POST /v1/music-router/generate. sume jobs status, result, and download still recover jobs you created over the API. Schedules have no CLI command at all. For running these commands unattended, see the Sume CLI in CI.
Sources
Related posts
Written by Sume