Feature Request: A frictionless, one-click "Report Broken Site" button in the extension (with automated log collection)
Hi everyone,
Let’s start by saying that 1Password’s autofill ("The Brain") is genuinely fantastic most of the time. But when a site changes its login layout, an A/B test rolls out, or a weird custom form breaks, autofill fails.
When that happens, what is the current user experience?
-
Realize it's broken.
-
Dig through menus to find "Collect Page Structure."
-
Save the JSON file to your computer.
-
Open an email client, write up the issue manually, attach the JSON file, and send it to Support.
That is a lot of friction for a busy user. Because it's so tedious, most people just right-click, fill it manually, and move on with their day. 1Password loses valuable telemetry on broken sites, and users are left wondering why their favorite tools aren't playing nice.
Can we streamline this? Here is why adding a native "Report Broken Site" button directly inside the extension menu would be a massive win for everyone.
Why this feature is desperately needed
-
Massively Lower Friction = Better Data: If reporting a broken form takes two seconds instead of two minutes, the volume of accurate reports will skyrocket. Instead of a trickle of manual emails, 1Password engineering gets a steady, crowdsourced pulse of what sites are breaking in the wild.
-
Proactive Rather Than Reactive: Right now, 1Password often only finds out a site is broken when enough users complain or support tickets spike. A streamlined reporting flow catches layout breakages on niche or regional websites before they become widespread complaints.
-
Keeps Users in the Ecosystem: When a feature is hard to use, users blame the product. Making it seamless to report issues shows that 1Password cares deeply about reliability and polish.
How it could work (Privacy First)
We know privacy is 1Password’s whole brand, so any reporting tool would need to be built with strict safeguards:
-
Sanitized Logs: Automatically strip out any sensitive user data, passwords, or personal info from the page structure JSON before it ever gets bundled.
-
One-Click Feedback: A simple sub-menu in the extension: Report Site Issue -> Select what went wrong (Didn't autofill / Filled wrong field / Saved wrong password) -> Submit.
-
Optional Context: A single optional text box for notes (e.g., "The 2FA field gets skipped entirely").
The Bottom Line
A password manager is only as good as its ability to seamlessly log you into things. By building a direct bridge between users experiencing a broken site and the engineers who fix them, 1Password can make autofill bulletproof.
If you’ve ever rolled your eyes when an autofill failed and didn't bother reporting it because it was too much work, please drop a vote or a comment below so the product team sees how much we want this!