Install issue reporting with the wizard
The wizard writes the reporting snippet into your own codebase — you pick the framework, it produces the change.
Nothing reaches the workspace until your application reports to it. The wizard is what makes that happen: you tell it what the application is written in, and it produces the exact change for your codebase — the package to add, the line that initialises reporting, and the project key already filled in.
What the wizard asks
- Which project — pick the project the reports should land against. Everything the wizard generates is keyed to it, so two applications never share a stream.
- Which framework — Laravel, Django, Express, Next.js, Spring Boot, Rails, .NET, React Native, and the rest. The instructions change with the answer; the key does not.
- How to apply it — copy the snippet into your code yourself, download the prepared package, or let the workspace write it over an FTP/SFTP connection you have already approved.
- Confirm — send one test error and watch it arrive. Until it does, the wizard does not claim the project is connected.
What lands in your codebase
A dependency and a few lines at your application’s entry point. No agent runs beside your process, nothing is injected at runtime, and the change sits in your version control like any other commit — reviewable, and revertible by reverting it.
After the wizard
The first errors usually arrive within a minute, and the backlog your tracker has been holding follows on the next sync. From there the workspace groups them, explains what broke, and scores what is worth acting on.