Change the status of an agent feedback report
Move a report along. A new report can be accepted or dismissed, an accepted one fixed or dismissed, and a fixed or dismissed one reopened to new. The move is written to the administrator log.
Only an administrator of this instance can use this endpoint, and only with an API key that carries the administration scope by name. Anybody else, including an administrator whose key does not carry it, gets 404 as though the endpoint did not exist.
Parameters
Sent as JSON. Anything not listed here is ignored.
The id of the report, of any account on the instance.
The status to move to: new, accepted, fixed or dismissed. A move the current status does not allow answers 422 on status, naming both statuses.
Returns
The report object as it stands now, without its notes. Read the report to get them.
The report.
Always agent_feedback_report. It names the kind of record, so a caller holding several kinds can tell them apart without looking at where they came from.
The id of this record, as a string even when it reads as a number. It is what every endpoint naming this record takes.
Everything the record holds.
The number administrators read the report by, such as 48 for #48.
new, accepted, fixed or dismissed.
bug, missing_tool, unclear_description or improvement.
blocks_task, needs_workaround or minor.
One line naming the problem.
The MCP tool the report is about, as the agent wrote it, or null.
What the person asked, paraphrased by the agent, or null.
The tool calls the agent tried, in order. An empty list when it sent none.
One tool call.
The tool it called.
The arguments it sent, as the agent wrote them, or null.
success or error.
What came back, or null.
What happened.
What should have happened.
The fix the agent suggests.
Code the agent suggests for the fix, or null.
The model the agent says it runs on, or null.
The connected assistant or the API key the report came through.
The account the agent was working in.
Who the agent was working for, or null once their user is deleted.
Their name.
Their email address.
When the report was sent, as a count of seconds since 1970.
Where to find this record.
The absolute address this record is read from.
Rate limit
Sixty requests per minute, per user, shared by every key and device. Every answer carries the budget left in X-RateLimit-Remaining.
Keys act as you, with exactly the access you have. Make one per integration so you can revoke it alone.