@getoncall/react

Browser error monitoring for React — with plain-English diagnoses and verified fix PRs.

Drop one component into your app and OnCall catches the errors your users actually hit, explains each in plain English, and — when you approve — opens a pull request that fixes it and confirms the fix held in production. Built for apps shipped with Lovable, Bolt, v0, Cursor, and Replit.

• 🪶 Loads a ~2KB async SDK — no bundle bloat, no dependencies
• ⚛️ One component (or one hook) — that's the whole integration
• 🔑 Uses your public project key (onc_pk_…) — safe to ship in the browser

Install — just ask your agent

In Cursor, Claude, Lovable, v0, or any AI editor, paste this (swap in your key):

Install OnCall in this React app — add @getoncall/react and render <OnCall projectKey="onc_pk_your_project_key" /> near the root. Nothing else.

Connect the OnCall MCP server (npx @getoncall/mcp) and your agent installs and verifies it for you — no code, no config.

Install

npm install @getoncall/react

Render <OnCall /> once, near your root

import { OnCall } from "@getoncall/react";

export default function App() {
  return (
    <>
      <OnCall projectKey="onc_pk_your_project_key" />
      {/* your app */}
    </>
  );
}

Prefer a hook?

import { useOncall } from "@getoncall/react";

function Root() {
  useOncall("onc_pk_your_project_key");
  return <YourApp />;
}

Either one mounts a tiny loader that pulls the OnCall SDK and captures uncaught errors, unhandled promise rejections, and console errors — with the route and a scrubbed breadcrumb trail.

Where do I get a key?

Create a project at intaglio.io and copy the public project key (onc_pk_…) from the install screen. It's a public identifier — safe to commit and ship in client code.

Also monitoring a backend?

Use @getoncall/node for server errors, or @getoncall/next on Next.js (client and server). Fastest of all: @getoncall/mcp — let your AI agent do it.

Links

• 🌐 Dashboard & docs: intaglio.io
• 🐙 Source: github.com/Booger-Aids/oncall

MIT © OnCall