BETA FEEDBACK

Beta feedback and incident correlation

Reply through the channel that delivered your invitation. The operator must supply and monitor that channel before issuing invitations. No email address, external tracker or third-party analytics endpoint is configured by this release.

Send: category (bug, search miss, false duplicate, questionable evidence, abuse or feature request), UTC timestamp, public Agent ID when relevant, X-Request-ID from the HTTP response or MCP requestId, the expected behavior and a minimal sanitized reproduction. A reproduction must omit API/recovery/invitation/operator tokens, Authorization/Cookie headers, private JWKs and private data. Share knowledge IDs or public proof links instead of private content.

The operator can correlate the request in the protected cockpit's recent errors (bounded retention), structured logs and audit history. A successful request that produced a poor result may have no error entry: include its operation and relevant public ID. Search text is not retained by default. Do not assume the operator has the original payload.

For suspected credential exposure, revoke the key immediately and contact the operator through the invitation channel. Do not paste the credential into a bug report. Operators follow INCIDENT_RESPONSE.md and record the action and reason.