What Makes a Bug Report Effective
Anthropic's support team receives a high volume of reports. Reports that result in faster resolution include:
- A reproducible path — exact steps from login to error
- The exact error text — copy the message, do not paraphrase
- Environment details — OS, browser, app version
- Scope information — is it all conversations or one? All devices or one?
- Isolation testing results — did it happen in incognito? On mobile?
Step-by-Step: How to Report a Bug
1. Reproduce and Document the Bug
Before reporting, try to reproduce the bug consistently:
- Start from a fresh browser session (incognito or after clearing cookies)
- Follow the exact steps that trigger the bug
- Record exactly what happens — the error message word for word, or the unexpected behavior
If you can reproduce it, note the minimum steps required (helps engineers isolate it faster).
2. Run the Basic Isolation Tests
Before reporting, check:
- Incognito test: Does the bug happen in a private window with no extensions? If not, an extension is the cause.
- Network test: Does it happen on a different Wi-Fi or mobile data? If not, your network is the cause.
- Device test: Does it happen on another device or browser? If not, the issue is local.
Include these test results in your report — "happens in incognito on Chrome and Firefox, does not happen on mobile" is far more useful than "happens on my computer."
3. Collect All Relevant Details
Gather before submitting:
- Error message: exact text, including any error codes (copy from the UI or browser console)
- Screenshots or recording: visual evidence is extremely helpful
- Browser and version: e.g., Chrome 124.0.6367.91 (find in Settings → About)
- OS: macOS 14.4, Windows 11, iOS 17.3, Android 14
- App version (if mobile): find in App Store or Play Store on your device
- Account email: the email you use to log into Claude
- Date and time: when the bug first appeared and how frequently it occurs
- What changed recently: new extensions, OS update, network change, Claude update
4. Submit the Report at support.anthropic.com
- Go to support.anthropic.com
- Click Submit a request or the relevant contact option
- Select the appropriate category (Technical Issue, Billing, Account, etc.)
- Fill in the subject line with a specific description: "Error loading chat — happens in all browsers since May 15"
- Paste your reproduction steps, environment details, and error text in the body
- Attach screenshots
- Submit
5. Respond to Follow-Up Requests Promptly
Support agents often need clarification. Check your email for replies and respond with any requested details quickly — delayed responses extend resolution time.
Bug Report Template
Use this template for your report:
Bug: [One-sentence description]
Steps to reproduce:
1. Log into claude.ai with [email/Google/Apple]
2. Open [new conversation / specific project / settings]
3. [Action that triggers the bug]
4. Error appears: "[exact error text]"
Environment:
- Browser: [Chrome 124 / Firefox 125 / Safari 17]
- OS: [macOS 14.4 / Windows 11 / iOS 17]
- Extensions: [none in incognito / list if relevant]
- VPN: [yes/no]
- Plan: [Free / Pro / Team]
Isolation results:
- Incognito: [yes, reproduced / no, works fine]
- Different browser: [yes / no]
- Different device: [yes / no]
- Different network: [yes / no]
First occurred: [date and approximate time]
Frequency: [every time / intermittent]
Account email: [your email]
Why This Matters
Vague reports like "Claude is not working" require back-and-forth clarification that adds days to resolution. Reports with exact steps, environment details, and isolation test results often allow engineers to reproduce and fix bugs on the first review. The 10 minutes you spend documenting properly saves everyone time.
Common Mistakes to Avoid
- Paraphrasing the error message — the exact text often contains diagnostic codes; copy it verbatim
- Reporting without testing incognito first — many bugs are local browser issues, not bugs; testing first saves a wasted report
- Not including browser and OS version — "Chrome on Mac" is not enough; specific versions matter for reproduction
- Opening multiple tickets for the same issue — creates confusion and slows response; one well-documented ticket is better than three vague ones
- Not following up when support requests more information — tickets that go without user response for 72 hours are often closed
FAQ
Q: How long does Anthropic typically take to respond to a bug report? Response times vary based on severity and support volume. Critical bugs affecting account access or billing typically receive a response within 24–48 hours. General bug reports for UI or feature issues may take several business days. Including all required information in your initial report — browser version, OS, steps to reproduce, isolation test results — significantly speeds up first response because engineers can often reproduce the issue without a follow-up question.
Q: Should I report a bug if I can only reproduce it sometimes? Yes, intermittent bugs are worth reporting. When documenting an intermittent issue, note the frequency (for example, "occurs roughly 3 out of 5 times"), what conditions seem to trigger it versus when it works correctly, and whether it happens across different browsers or devices. Intermittent bugs are harder to fix but they are real and engineers track them. More reports of the same intermittent bug help confirm it is worth prioritizing.
Q: Is there a community forum where I can check if others have the same bug? The r/ClaudeAI subreddit is the most active community for Claude users. Searching there before submitting a support ticket often confirms whether an issue is widespread and may surface workarounds faster than official support. The official Anthropic Discord is also active. If many users report the same issue simultaneously, Anthropic typically acknowledges it on status.anthropic.com.
Q: What should I do if my bug report ticket is closed without being resolved? If your ticket was closed but the issue persists, reply to the closed ticket with updated information rather than opening a new one. Reference your original ticket number. If you cannot reply to a closed ticket, open a new report and reference the previous ticket number explicitly. Providing any new information — such as the issue persisting after a browser update or on a different device — helps reopen investigation.
Prevention Tips
- Before reporting, test in incognito mode without extensions — this single step eliminates the most common false-positive reports
- Screenshot or screen-record the error at the moment it occurs, even if you plan to describe it in text — visual evidence cuts resolution time significantly
- Keep a brief log of when bugs occur (date, time, what you were doing) so patterns are easy to identify and communicate to support