Troubleshooting

Debug common Sume CLI auth, config, job, media input, and release issues.

Start with read-only checks:

Missing API key

Start with the browser login:

For remote or headless terminals:

For CI and server automation, you can use a manual API-key setup and environment variables:

Wrong API base

Do a check of the local configuration:

The current production API base is:

Job created but no result yet

Jobs are async. Poll the job status:

Get the result only after the job is complete:

If 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

Current 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:

  1. The URL is not HTTPS.
  2. The URL points to localhost or to a private network.
  3. The response is not an image.
  4. 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.