_runheed
Sign in

React and browser error tracking your coding agent can read

Updated 2026-11-13

Runheed accepts events from Sentry SDKs, including the browser ones, so a React, Vue, Svelte or plain JavaScript frontend reports through @sentry/browser (or @sentry/react): point its DSN at your Runheed project and your coding agent reads what broke in your users' browsers. Tested with @sentry/browser 11 in Chrome, sending from another origin.

Set it up

  1. 1.Install the SDK.

    terminalbash
    npm install @sentry/react
# or, for any framework: npm install @sentry/browser

  2. 2.Initialize it once, before the app renders, with the project's Sentry SDK DSN (Projects page, or ask your agent: runheed_list_projects). The DSN is public by design: it can only send errors to this project.

    src/main.tsxtypescript
    import * as Sentry from '@sentry/react';

Sentry.init({
  dsn: 'https://<key>@runheed.com/<number>',
  environment: import.meta.env.MODE,
  release: import.meta.env.VITE_GIT_SHA,
});

// Errors thrown while rendering: wrap the app in Sentry.ErrorBoundary.
// Errors you catch yourself: Sentry.captureException(err).

  3. 3.Connect your agent, then sign in when it asks (other clients: /connect).

    terminalbash
    claude mcp add --transport http runheed https://runheed.com/api/mcp

The npm and PyPI releases are not out yet, so these commands install the same package files straight from runheed.com. Nothing else changes when the registry versions ship.

What it catches

  • Uncaught errors and unhandled promise rejections in the browser
  • Render errors caught by Sentry.ErrorBoundary
  • Errors you report with Sentry.captureException(err), with the page URL and browser
  • Minified frames mapped back to your source files, lines and functions through the bundle's source map

What it does not do

  • Source maps are applied when your bundle's sourceMappingURL is public (in Vite, build.sourcemap: true), or when you upload the .map files to /api/sourcemaps from your build (see /docs#source-maps). Without either, frames show the minified bundle's file and column
  • Session replay and performance data are accepted and dropped: Runheed tracks errors only

Then ask your agent

> what broke in production since the last deploy? fix the top one and resolve it with the commit hash

Connect Runheed first: Claude Code, Cursor or another client. Then see how the agent fixes and resolves an error.

Common React and browser JavaScript errors

7-day trial, then $29/moOther agents and editorsCancel any time from the billing portal