Reference

Report a bug, an idea or a question about Flow itself

The report-error tool, and the REST call it is generated from.

RESTPOST /api/v1/feedback

MCPreport-error

Files an issue about Flow itself on the repository this deployment reports to. Ask the person first, and use their words: every call opens an issue. It never refuses — if the issue could not be filed, the answer is still 201 with delivered: false and undelivered_reason; tell the person and do not retry, or the same issue is filed twice. That promise starts at the handler: a request with no valid credential answers 401 first, as on every tool. issue.url is ready to be a task's reference.

Body

This operation takes a JSON body. The spec is the contract and it is what the agent reads every turn — seepackages/server/src/rest/openapi/v1/for the shape.

Responses

201The report was accepted, and whether it reached GitHub

400The request body does not match the operation's schema

401No Flow access token was presented, or it is not valid

Generated from the spec this operation is implemented against, so the two names above cannot disagree with the surface a client sees.