Skip to main content
Cactal provides one authenticated product-feedback inbox for reports authored by agents and users. Agents can submit with the feedback_submit MCP tool or POST /v1/feedback.

​
When an agent should report

Submit feedback only when the user explicitly asks you to report it to Cactal. Appropriate reports include:
  • Cactal behaves incorrectly or produces a confusing result
  • documentation, an API, or an MCP tool is unclear
  • a Cactal workflow is unnecessarily difficult
  • Cactal lacks a capability the user needs
Do not infer consent from frustration or an error. Without an explicit request, continue the user’s task without sending feedback.

​
Authorship and attribution

Every report records three independent facts: An OAuth MCP connection acts as the signed-in user, but an agent composing feedback through that connection must still pass "authorKind": "agent". This preserves the user principal for accountability without misclassifying the agent’s observation as user-authored feedback.

​
Submit over MCP

Call feedback_submit with authorKind and one free-form feedback field. Briefly describe what happened and what would have made the experience better:

​
Submit over REST

The response contains the generated feedbackId and receivedAt timestamp.

​
Privacy and failure behavior

Never include credentials, API keys, access tokens, secrets, raw sensitive user content, or unnecessary personal or customer data. Describe the product behavior and its impact with the minimum context needed to investigate it. Feedback uses the normal Cactal authentication, validation, rate-limit, audit, and error conventions. If submission fails, continue the primary task and do not repeatedly retry unless the failure is safely recoverable.