Bug reports
Report a bug from the desktop app, the web, or iPhone, and learn when a report earns extra usage.
Open the form
In the desktop app and on the web, Report a bug is under your account at the bottom of the sidebar. The form opens over your current chat, or as a sheet in a narrow browser window. On iPhone, Report a bug is in the account menu, or you can shake your iPhone. Shake to report is on until you turn it off in Settings → Report a bug.
Settings also has a Report a bug page. In the desktop app, it’s in the Shared group, after Updates. On the web and on iPhone, it’s with the other sections.
Fill out the report
- App — PC, Web, or Mobile. The app you’re using is already selected.
- Section — Code, Chat, Agents, Files, Settings, or Custom in the desktop app and on the web. On iPhone: Chat, Remote, Agents, Files, Settings, or Custom. Custom asks for a short name.
- Report — up to 1,000 characters. Describe what you did, what you expected, and what happened. Steps to reproduce the problem help more than a summary.
- Dictate — the microphone under the text box. You can edit while it records and discard a recording. Each report allows one minute of audio in total. Dictation uses the lowest-cost transcription model in the catalog, not the model you chose in Speech settings.
- Screenshots — up to three. Choose, paste, or drop them onto the form. Each one is scaled down on your device before it’s sent, so a full-screen capture is well under 1 MB.
- Include diagnostics — on by default. Sends a redacted snapshot of app and device details and recent errors. Turn it off to send only what you wrote.
You can leave a field empty and come back to it later. The form won’t accept text that looks like a password, an API key, a token, a private key, a connection string, or an environment variable assignment. Describe the problem without the secret. You can send one report per minute, and the form shows how long to wait.
Your recent reports is collapsed. Open it to see up to five of your reports.
After you send a report
An automated reviewer reads the text with zero data retention and no-training filters on. It rejects spam, harmful content, and reports that aren’t a new bug. Rejected text isn’t stored. If the reviewer is unavailable, the report is saved for later review and doesn’t earn a credit yet. You see the same confirmation either way. A credit is the only sign that a report was accepted.
Credits
- The first new, actionable report each day (UTC) adds $0.50 of extra usage.
- The seventh new, actionable report in a rolling seven days adds $1.00, at most once per calendar week. One report can earn both.
Duplicates, feature requests, and reports without enough detail to investigate don’t earn credits. Review decisions are final. Credits are extra usage under the Terms of Service and have no cash value.
Data retention
Reports are linked to your account so we can follow up. The reviewer sees only the text you wrote. Our team also sees the diagnostics and screenshots. Check screenshots for private information before you attach them. Screenshots are deleted after 30 days. Reports and their diagnostics are deleted after 90 days. If a report is rejected, its text isn’t stored and its screenshots aren’t uploaded.