CLI
Troubleshooting
Debug common Sume CLI auth, config, job, media input, and release issues.
Start with read-only checks:
sume version
sume auth status
sume doctor --agent --json
sume account get --jsonNot signed in
Start with the browser sign-in:
sume login
sume auth statusFor remote or headless terminals, sign in with a code:
sume login --deviceYour Sume sign-in expired. Run sume login. means the refresh token was
revoked, reused or more than 30 days old: run sume login again.
For CI and server automation, you can use a manual API-key setup and environment variables:
sume auth setup --api-key "$SUME_API_KEY"export SUME_API_KEY="sume_live_..."
export SUME_API_BASE_URL="https://api.sume.com/v1"Wrong API base
Do a check of the local configuration:
sume doctor --agent --jsonThe current production API base is:
https://api.sume.com/v1Job created but no result yet
Jobs are async. Poll the job status:
sume jobs status <job_id> --agent --jsonGet the result only after the job is complete:
sume jobs result <job_id> --agent --jsonIf a local wait timed out, examine the job before you submit another paid job.
Image / Video / Music CLI command missing
The shipped CLI has no sume image, sume video, or sume music subcommand.
Submit those families through the Developer API
(Image, Video, Music). Then
use sume jobs status / sume jobs result to recover the job.
Local MCP not launched
sume mcp doctor --jsonCurrent releases report coming_soon. For Cursor/Claude, use
hosted MCP at https://mcp.sume.com/mcp. Or, use the CLI commands
directly.
Media input rejected
Avatar media fields must contain public HTTPS image URLs. For Avatar 1.0 photo
input, use --type photo --image-url https://.... For Avatar Video, use
--product-image https://... or --scene-image-url https://... when
necessary.
Frequent causes:
- The URL is not HTTPS.
- The URL points to localhost or to a private network.
- The response is not an image.
- The URL must have cookies, auth headers, or a short-lived signature. The signature expires before Sume can fetch the URL.
Do not paste private media URLs, signed URLs, or auth headers into public logs.
Report an issue
Include this data:
- The command name and flags, with the secrets redacted.
sume version- The sanitized error code/message.
- The request id, if there is one.
- The job id, if the issue is job-specific.
- The source of the auth: env or local config.
Do not include API keys, signed URLs, private media URLs, raw provider payloads, emails, or workspace/user ids.