Difficulty in identifying and fixing bugs without access to source code

Signals over time

2 observed signals across 1 sources, tracked for 3 days. Confidence: low.

What people are saying Observed

• “I’m building AnnotateFix to bring customer bug reports and browser evidence to your coding agent. A customer says the discount button doesn’t work. You open Cursor, but the report doesn’t tell you what they clicked, what the browser logged, or which request failed. You still have to piece that together before the agent can help. I’m Bolaji, the founder of AnnotateFix. I built it because shipping an app with AI has become much easier than maintaining it once real customers start using it. AnnotateFix lets customers point at the broken element inside your app and report the problem. The widget attaches screenshots, recent actions, console errors and failed requests. Its MCP tools make reports, redacted browser evidence and QA tasks available to coding agents alongside your codebase. The workflow we’re building toward: reproduce the reported failure in a test, prepare a focused fix, then review what changed and whether that same test passes. I’m looking for Cursor users to try the early-access workflow with a real customer-reported bug. Explore the sandbox , which replays recorded test results and simulates PR review, or join the early-access waitlist . 1 post - 1 participant Read ful”

  RSS Feeds · request

• “There's honestly not much to say--I just described the bugs and it fixed them. This was just Opus 5. I put a stripped transcript here in case you want to look: https://nvidiot.net/ai/rdp-bugfixes.html I'm pretty familiar with reverse engineering and for most of my career I doubt I went more than a month without patching some memory into 0x90. The explanations are perfectly reasonable and are close to what I expected. It's just that it would have taken me a week to find where to patch without the source!”

  Hacker News · frustration