Agent-readable docs index: /docs/llms.txt. Full docs in one file: /docs/llms-full.txt. Download /docs/docs.zip to grep all markdown files locally.

Quickstart

Work through this checklist end to end and you'll have problems showing up in your dashboard, investigated for you.
  1. Create a workspace
    Sign up and create a workspace. It's the home for your team and everything Interfere finds.
  2. Create a surface
    A surface is one app you want Interfere to watch: a frontend, a backend, or a marketing site. Create one and copy its keys into your environment:
    • INTERFERE_PUBLIC_KEY: used by the SDK to send telemetry. Safe to expose.
    • INTERFERE_API_KEY: used to upload source maps in CI. Keep it server-side.
  3. Install the SDK
    Point your coding agent at the Interfere install prompt and it wires everything up. Run the command for your agent:
    curl -sL https://interfere.com/prompts/onboarding/v8/onboarding-nextjs.md | claude -p "Add Interfere to this codebase"
    On Vite, swap onboarding-nextjs.md for onboarding-vite.md. Want to read the prompt first? Open it directly:
    Next.js install prompt
    Covers Next.js, NestJS, and other Node backends.
    Vite install prompt
    Covers Vite and React apps.
    You can also open Ask AI at the top of these docs and ask it to install Interfere in your project.
  4. Connect your integrations
    Integrations give Interfere the context to investigate and a way to reach your team. From Settings → Integrations, connect:
    • GitHub so a problem ties back to the commit that caused it.
    • Your deploy platform (Vercel or Cloudflare) so problems line up with releases. On AWS, Fly, or your own servers, use the CLI instead.
    • Slack to get problems where your team already works.
    See all integrations.
  5. Deploy
    Ship your app. Once it's running, events start flowing and your first problems appear in your workspace, already grouped and triaged. Trigger an error to confirm the whole path end to end.

Not seeing events?

The SDK tells you what it's doing, so a quick check usually explains it.
Turn on debug logging
Set INTERFERE_DEBUG=1 to print lifecycle events at startup: when the SDK initializes, the release it resolved, and any exporter errors. It's the fastest way to see whether data is leaving your app.
Nothing in development
The Next.js SDK stays quiet outside production so local noise doesn't reach your dashboard. To capture while testing, call init({ enabled: true }) (on Vite, gate it with import.meta.env.PROD). See each SDK's FAQ.
A "no release slug" warning
The collector needs a release to attach telemetry to. The Next.js and Vite plugins upload one during the build automatically. On a backend or a custom platform, run the CLI as a postbuild step (interfere sourcemaps upload ./dist) with INTERFERE_API_KEY set.
Telemetry blocked by an ad-blocker
Some ad-blockers drop requests to telemetry endpoints. Set apiHost on the SDK to a subdomain of your own site — a CNAME to the target shown in your dashboard — so telemetry posts to your own origin. See the Next.js or Vite SDK guides.
Still stuck? Reach out at support@interfere.com.
Interfere
Powered byHolocron