Skip to main content

Report a problem from the CLI

Use a Compute report for a failed or stuck run, a billing question, or an unexpected CLI or MCP error. The report stays linked to your signed-in account, and adding a run id gives the operator the run’s current status, provider, machine, and error context.
Replace the example ids with the values from your error. Available categories are run_failed, boot_failed, billing, cli, mcp, docs, and other. Run compute report --help for the optional --error-code and --exit-code fields. Use --details - to read longer details from standard input. The command prints a report id beginning with rpt_. Some known problems receive an automatic answer immediately. Otherwise, keep the id and check for an operator reply:
A report can be open, answered, or closed. Run the status command again later while it is open.

Report through an agent

With either Compute MCP server connected, ask the agent to call compute_report_issue with a category, short summary, and the run_id when a run is involved. It should show you the returned rpt_ id and any immediate response. Later, ask it to call compute_get_report with that id for the current status and operator reply. An agent using the CLI can run the same compute report and compute report status commands shown above.
Reports are stored and shown to operators, and GitHub issues are public. Never include COMPUTE_API_KEY, config.toml, session tokens, Checkout session ids, secret values, or signed upload and download URLs. The report API rejects several credential-shaped values, but it cannot replace checking the text before you send it.

What to include

  1. Run id — from compute run or compute runs list. Pass it with --run.
  2. Request id and error code — from the API error body.
  3. Command and expected result — include the entrypoint, GPU selection, and what happened instead.
  4. Approximate UTC time — especially for intermittent failures.
Before filing, these checks may narrow down the problem:
If a run is terminal and compute machines is empty, teardown completed even when the function failed. File the report anyway if the result or receipt looks wrong.

Contact, public issues, and status

Terms and Privacy are published on the product site.