Report a bug

Tell us what went wrong in your own words, or paste what your agent wrote. Kater writes the report. A Kater engineer reads it, and you follow it to the fix.

Audience

Everyone who uses Kater

Prerequisites

None. You can send a report without a Kater account.

Send a report

New bug report

Other places to report a bug

Every place opens the same report. Each one attaches what it knows, so you type less.

Web app Select your name at the bottom of the sidebar, then Report a bug. Kater attaches the page you have open.
An error message Select Report this bug under the message. Kater attaches the error.
Admin console Open Bug reports to see every report from your organization.
Your agent Ask it to report the bug to Kater. The Kater MCP writes the report, and you check it before it goes.
CLI Run kater report in a terminal.
VS Code Run Kater: Report a bug from the command palette.

What happens after you send it

Sent. An engineer reads every report. If something is not clear, they ask you on the report page.
Reproduced. Kater runs your steps and adds them to our tests as a check. The check fails until Kater fixes the bug.
Fix in progress. We tell you about each change by email, or by Slack DM if your team uses Kater in Slack. You also see each change on the report page.
Fixed. You confirm the fix. If you said yes, your name goes in the changelog.

Open reports

These are reports that other teams shared. If a bug happens to you too, select Me too. More teams move a bug up the list, and we tell you when Kater fixes it. Select it again to remove your Me too.

Sign in to see open reports Open reports come from other Kater teams. Sign in to read them and add a Me too. Sign in You can send a report without an account.

What other teams can see

Other teams see the title, the status and the Me too count. They do not see your name, your company, your page address or the files you attached. Your name shows only in the changelog, and only if you say yes.