Set it up with Claude Code or Copilot in one prompt

Updated 1 October 2026 · BugsRadar team

The docs are written so that a coding assistant can follow them. Give Claude Code, Cursor, GitHub Copilot or whatever you use one prompt in the project's folder, and it reads the guide for your platform, installs the package, connects it to the logging the project already has, and sends a test error. You review the diff and press merge.

What you do first

Create a project and a channel at app.bugsradar.com and put the project's API key into the BUGSRADAR_KEY environment variable. An assistant can't do this step: it has no account, and the key must never end up in a file it would commit. See Keep the API key secret.

The prompt

Add BugsRadar error alerts to this project.
1. Read https://bugsradar.com/docs/ and pick the guide for this project's platform: .NET, Node.js, Python, or plain HTTP for scripts.
2. Install the package and connect it to the logging the project already uses and to uncaught errors.
3. Read the API key from the BUGSRADAR_KEY environment variable. Never write the key into code or into files that get committed.
4. Use BugsRadar only in code that runs on servers, never in browser, mobile or desktop apps.
5. Send one test error, then tell me what you changed.

The prompt is the one from Get started. It names the rules an assistant tends to break on its own: the key comes from the environment, and BugsRadar goes only into code that runs on servers.

What the assistant does

• Reads the docs page for the platform - .NET, Node.js, Python or the HTTP endpoint - and the page for the logger it finds in the project: Serilog, NLog, log4net, winston, pino, loguru.
• Installs the package and registers the client once, with the key from the environment variable.
• Connects it to the existing logging and to uncaught errors, which is usually one or two lines in the place where the application starts.
• Sends one test error. It arrives in your channel within seconds, which is the proof that the wiring is right.

For assistants, the site also has an llms.txt: a short map of the docs with the rules for the key, so an assistant that reads it first doesn't have to guess.

What to check in the diff

• The key is read from configuration or the environment, and no file in the commit contains it.
• BugsRadar is registered in server-side code only: not in a browser bundle, not in a desktop or mobile app you ship.
• The logger that was already there is still there; the package adds a provider, a sink or a transport, it doesn't replace your logging.
• The test error arrived, and its message says what you expect: the project name, the level, the stack trace.

What it doesn't do

An assistant can't create the account, can't pick the chat the alerts go to, and shouldn't be the one deciding what is logged at Error. Those stay with you; the typing is what it saves.

Where to go next

The prompt lives in Get started. Go, PHP, Ruby, Java covers platforms without a package, where the assistant writes the HTTP call instead.