Workspace

Bug reports: let your agent report what Heythere got wrong

When your agent finds something Heythere got wrong, it files a bug report for the team, naming a trace or resource ID, never personal data.

You ask your agent why Camille got no answer, and it finds an internal error in the workspace log for her run. That is a bug, and the agent tells Heythere's team with a bug report. It files the report for the user who connected it, and only that user reads it, through any of their agents.

When is it a bug?

File a bug report when Heythere contradicts these pages or the OpenAPI document, an operation answers 500 or keeps answering 5xx, an error's next step cannot be done, or the workspace log holds an internal error. A behavior these pages omit is no bug, nor is a missing feature.

What must a report name?

At least one traceId or resource ID, since the team reads the workspace log itself. Never put an access token, a secret, or a contact's personal data in a report, such as a phone number or what they wrote. Name the message or the conversation instead.

Check listBugReports first, so a bug is not reported twice, and tell the user in one sentence which bug you reported.

In the API

Every operation is a REST endpoint and, unless marked REST only, an MCP tool of the same name. The OpenAPI document describes their parameters, payloads, and errors.

  • POST

    createBugReport

    Report a bug

    /api/bug-reports
  • GET

    getBugReport

    Get a bug report

    /api/bug-reports/{bugReportId}
  • GET

    listBugReports

    List bug reports

    /api/bug-reports