Skip to main content
A coding agent connected over MCP can send feedback about Overmind itself: an operation that fails or contradicts its description, unclear guidance, a missing capability, stuck work, or repeated attempts without progress. Reports go to the Overmind team. They describe how the platform behaved, not what your data holds.

Turn it on or off

Agent feedback is one choice for your account. It covers every coding agent you connect. Until you choose, and after you choose Don’t allow, submit_feedback is not in the agent’s tool list and nothing is sent. Guest workspaces never send reports.

What a report contains

The agent fills these fields. Text fields have length limits, and the schema accepts no other fields. Overmind adds what it observes on the connection: the client name, the User-Agent and MCP-Protocol-Version headers, the credential type and the MCP contract version. Each report is linked to your account and, when given, to the project.

What is kept out

Agents are told to leave out data rows, prompts, code, file contents, paths, customer names and credentials. Before a report is saved, Overmind replaces:
  • known credential and key formats with [credential removed]
  • email addresses with [email]
  • web links with [link]
  • home-directory paths with [path]
  • IPv4 addresses with [ip]
Other text is saved as the agent wrote it. Overmind cannot detect every customer detail in free text, such as a name or an amount. The agent shows you a line for each report it sends, with the link to Settings.

Limits

An account sends at most 20 reports an hour. A report sent again with the same report_id updates the earlier report. On a self-hosted deployment, reports stay in that deployment’s own database.