Submit a hosting provider bug report from log warnings with Claude in Chrome

Posted

Sep 28, 2026 by Nathan Broadbent (@ndbroadbent)

·

Last checked

Oct 16, 2026

·

Method:

How we verify

Evidence: Screenshots or logsThe source shows screenshots, a transcript or the agent's output.

Outcome

Using the poster's logged-in browser, Claude in Chrome submitted a bug report to DigitalOcean after finding warnings in the logs.

Agent

Claude in Chrome

The source didn't share its exact prompt, so we wrote this from what it describes.

Here's a task I'd like your help with. Read it all the way through before you start.

Goal: Check these logs, and if they show a real problem with my provider, file a bug report with them.

Check with me first: Which service and logs should you look at?

What I'll give you:
- The logs or where to find them
- My provider account (I'll stay logged in)

Rules:
- Explain the warnings you find before writing anything.
- Write a clear bug report with the relevant log lines and remove any secrets or personal data.
- If something is missing or unclear, ask me instead of guessing.
- Show me the report before submitting.

Output: A summary of the warnings and the bug report, submitted only after my OK.

You'll know it worked when: the provider has a clear report with the evidence it needs.

Here's a task I'd like your help with. Read it all the way through before you start.

Goal: Check my service logs and, if they show a real provider problem, file a clear bug report with them.

Quick check first: tell me if anything below is missing or unclear.

Inputs (fill in or confirm):
- Logs or log location
- Service and provider account (I'm logged in)
- Time window
- Provider's support channel

Rules:
- Explain each warning in plain words and whether it points to my config or the provider.
- Only proceed to a report if evidence points to the provider.
- Write a report with timeline, affected resource IDs, log excerpts and steps to reproduce.
- Strip secrets and personal data from excerpts.
- Include my environment details (region, version) in the report.

Checkpoint: Show me the report before submitting.

If you get stuck: If you need more access, ask. If a login, CAPTCHA or two-step code appears, stop and ask me to handle it; never guess or store passwords.

Verify before you finish: Check the excerpts match the timestamps.

Output: Diagnosis and the draft report.

Done when: the provider gets a clear, evidence-backed report.

Source

https://x.com/ndbroadbent/status/2104499860368138397