Errors and failed requests, quietly delivered to your corner.
You know the ritual. Something breaks, you hit F12, and your app reflows into a thumbnail of itself while you dig through the console for the one line that matters. Most of the time you did not need the whole toolbox; you just needed to see what broke.
Racna handles that part. It is a Chrome and Edge extension that passively captures JavaScript errors, failed network requests, console warnings, and unhandled promise rejections on pages where you enable it, and drops them in a small overlay panel that stays out of the way until something is worth looking at.
It is not a DevTools replacement. When you need deep inspection, DevTools is still the right tool. Racna covers the moments before that: a tab you left running, a colleague's machine, that one page that only misbehaves while the console is closed.
Console errors and warnings, uncaught exceptions, unhandled rejections, and failed fetch / XHR requests.
Navigation, clicks, logs, and HTTP traffic preceding each error, for context.
Pattern-match the noise away so the panel only counts what you care about.
Surface specific patterns as toast notifications the moment they appear.
Markdown copy and export, with one switch that restructures it for AI debugging tools.
Off everywhere by default, except localhost. Runs only on sites you opt
into.
Racna stays out of the way until you switch it on for a site from the toolbar popup.
Out of the box only localhost and 127.0.0.1 are enabled, so
your everyday browsing is untouched.
When something breaks, a badge appears. Open the panel to see each entry with its stack trace and the breadcrumbs that led up to it: recent navigation, clicks, logs, and HTTP calls.
Every entry copies as clean Markdown, with per-field toggles for what to include. Flip the "AI" switch and the same copy becomes a structured document for your AI tool of choice: error first, fenced sections, a breadcrumb timeline, and credential headers masked. Copy All exports the lot at once.
That same failed request, copied both ways:
Default Markdown
PAGE: http://localhost:8000/
BREADCRUMBS:
15:04:07 CLICK button.net "XHR GET httpbin.org/status/500"
15:04:07 HTTP GET https://httpbin.org/status/500 → 0 (115 ms)
REQUEST: GET https://httpbin.org/status/500
RESPONSE: Network Error Network Error (115 ms)
CALL STACK:
Error
at XMLHttpRequest.send (chrome-extension://nnhhmjniggmgoabcnmaafkfifiinimnp/interceptor.js:297:24)
at fireXhr500 (http://localhost:8000/:640:11)
at HTMLButtonElement.onclick (http://localhost:8000/:391:56)
AI format
REQUEST: GET https://httpbin.org/status/500
RESPONSE: Network Error Network Error (115 ms)
CALL STACK:
```
Error
at XMLHttpRequest.send (chrome-extension://nnhhmjniggmgoabcnmaafkfifiinimnp/interceptor.js:297:24)
at fireXhr500 (http://localhost:8000/:640:11)
at HTMLButtonElement.onclick (http://localhost:8000/:391:56)
```
TIMELINE (oldest first, ends at this failure):
```
15:04:07 CLICK button.net "XHR GET httpbin.org/status/500"
15:04:07 HTTP GET https://httpbin.org/status/500 → 0 (115 ms)
15:04:07 FAIL this entry (see above)
```
PAGE: http://localhost:8000/
Watch rules turn specific patterns into toast notifications: a URL you are debugging, a message you are waiting for. Ignore rules do the opposite and keep known noise out of the count.
Set up the rule
It fires as a toast
Selection mode lets you pick a set of entries and export them together as Markdown, handy for bug reports or a teammate's inbox.
Racna sends no telemetry and makes no network requests of its own. Captured events live in the tab's memory and disappear with it. Your rules and settings are stored in the browser's own sync storage, nowhere else. There is no server behind this extension. The full detail is in the privacy policy, and the source code is there to check.
Prefer building it yourself? It takes a minute:
git clone https://github.com/Niki-Mozzon/racna.git
cd racna
npm install
npm run build
Then open chrome://extensions (or edge://extensions), enable
Developer mode, choose "Load unpacked", and point it at the dist/ folder.
The repo ships an interactive playground: a page full of buttons that throw errors, fire failing requests, and flood the console on demand. Once Racna is installed and enabled there, it is the quickest way to see every capture path in action.