Report what went wrong
feedback_submit_reportSubmit an incident report after attempting resolution, including diagnosis, outcome, and tooling gaps, to help improve future tooling.
Instructions
Record your account of an incident this session opened — you will see one as an ISSUE_OPEN event on a tool result. Call it AFTER you have tried to resolve the problem, so you can say how it turned out; report it whether or not you succeeded, because a failure you could not rescue is the more useful of the two. tooling_gap is the most valuable field: it is what changes the tools you are given next time. Do not paste payload values into any field — name the JSONPath instead; values are stripped either way.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| outcome | Yes | ||
| attempted | No | What you tried, in order, including what did not work. | |
| diagnosis | Yes | What you concluded was actually wrong. | |
| session_id | Yes | ||
| incident_id | Yes | From the ISSUE_OPEN event, or from feedback_list_reports. | |
| tooling_gap | No | What would have let you resolve this faster. | |
| suspected_cause | Yes |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| state | Yes | The **derived** state. If it disagrees with your `outcome`, the report keeps both — that disagreement is itself a finding. | |
| events | No | What has happened in this session since your last call — the participant's callbacks, steps sent automatically, refusals, form submissions. Attached to every session-scoped result and delivered exactly once, so read it here instead of polling. Absent when nothing happened. `more` above zero means call record_get_events for the rest. | |
| message | Yes | ||
| accepted | Yes | ||
| incident_id | Yes |