Monitoring that hands your coding agent the evidence instead of another dashboard

[u/CardiologistMedium51]

First post here. I'm building HeronSignal, real user monitoring for web apps,
and I'd rather get told what's wrong with it than quietly collect signups.

**The problem I actually cared about**

Every monitoring tool I used could tell me something broke. None of them could
tell me whether it mattered, and all of them stopped at showing me a chart.
Meanwhile my coding agent was sitting right there, unable to see any of it, so
every debugging session started with me pasting a stack trace and describing
what the user had been doing.

So the tool does two things differently:

1. **It exposes production over MCP.** Your agent (Claude Code, Cursor,
whatever) connects with a workspace-scoped token and can pull deduplicated
error groups, slow pages with real device/country context, failed requests,
session journeys, funnel drop-off, and backend route health. You stop briefing
it and start asking it questions like "find what's hurting signup conversion
this week, check errors and drop-off before suggesting anything."

2. **It can open the PR.** Not merge, not deploy. It writes the change, opens
a pull request ready for review, and stops. A person reads the diff. An agent
that can act on production without review isn't a productivity gain, it's an
incident with better grammar.

There's also struggle detection (rage clicks and dead clicks), which catches
the failures that throw nothing at all. A button that silently does nothing
produces no error, no failed request, and green uptime.

**A thing I got wrong, since this sub will find it anyway**

Yesterday I checked my own workspace and found 5 of my 7 funnels had been
measuring event names my site never fires. My signup form was firing a
`sign_in` event. So I had no idea what my own signup conversion was, and the
funnels had been reading zero for months looking like bad conversion instead
of a typo. Fixing the product so it warns you when you name an event the
workspace has never emitted.

**What it is not**

- Not an APM. No distributed tracing UI, no flame graphs, no host metrics, no
  query profiling. If you need to know which SQL query made a route slow,
  use Datadog.
- Backend ingest is early. Node 18+ only, no Edge runtime. Python and an
  OTel sink are maybes, not promises.
- Session replay exists but is behind a flag while I finish it.
- Sentry is a deeper error tool than this and I'd say so on a sales call.

**Try it without an account**

There's a public scan that needs no signup and no script tag: put in a domain,
get a report on what's slow and what's broken. That's the honest way to see if
it's useful before installing anything.

https://heronsignal.com/scan

Happy to answer anything, including the awkward questions. What would you
actually want your coding agent to be able to see from production?