Status and resolution feedback

Create a client with createProblems({ slug: "acme" }) as shown in the MCP or CLI guide.

Check status and report an outcome

Keep the problemId returned by report() to check for an answer later or record what happened after trying a fix:

const status = await problems.getProblem(problemId);
if (status.ok && status.answer) {
  console.error(status.answer.title);
  for (const step of status.answer.steps) console.error(step);
}

// Call only after observing this outcome in your integration.
const feedback = await problems.verify(problemId, {
  result: "resolved",
  taskCompleted: true, // omit if the overall task outcome is unknown
  notes: "The deployment completed after applying the suggested fix.",
});

getProblem() returns the current status, optional answer, retryRecommended, and updatedAt. A recommendation is guidance for your integration; the SDK does not retry the failed operation or poll for updates.

verify() accepts resolved, not_resolved, partially_resolved, or unable_to_verify. Receiving an answer does not establish that it worked. Task completion is a separate optional boolean: omit it when unknown. Verification returns an acknowledgement in status and message; use getProblem() for the problem’s current lifecycle status.

Both methods resolve { ok: false, reason } on failure, honor reporting opt-out, and use timeoutMs and the shared HTTP 429 backoff. They do not consume the report attempt budget, cache their responses, or retry automatically. Successful status reads and verification clear cached reports for that problem so a rejected fix is not reused. Optional notes are redacted locally and limited to 4,000 characters; avoid including sensitive data.

MCP answer blocks include the report ID, answer ID, and status URL. Integrations can use these references to connect later feedback to the original report. With a custom endpoint, status and verification use sibling problems/<id> and problems/<id>/verify paths under the same prefix as report; query strings are not forwarded. The proxy must route these endpoints too.