Skip to content

Bug report from a log, secrets removed in your browser

Free

Paste a stack trace, CI log or HAR file. Tokens, keys, passwords, emails and IP addresses are removed in your browser before anything is sent. You get the error, where it failed and a report you can file.

Drop a file here
A log, text or .har file, up to 200 KB
Secrets are removed in your browser before anything is sent.
The report appears here

Paste a log or drop a file, then read it.

Your agent can call this as report_from_log when a test or build fails.How an agent uses this

How it works

Paste the log

A stack trace, CI log, browser console or HAR file. No log? Switch to Describe the bug and write what happened.

Check what was removed

The list shows each token, password, email and IP that was taken out, and its line. Open the cleaned text to see what will be sent.

Get the report

Only the cleaned text is sent. You get the error, the failing frame and a report to copy as Markdown, for GitHub or for Jira.

What it reads

It finds the error in the text you paste and the facts around it.

Up to 200 KB or 20,000 lines at a time.

You pasteIt finds
Anything with secrets in itTokens, keys, passwords, cookies, emails and IP addresses are removed in your browser before anything is sent. You see each one.
A stack traceThe error, the failing frame with its file and line, and the language.
A CI logThe failing step, the failed test and the runner's operating system.
A browser consoleThe error and the browser it came from.
A HAR fileThe failed requests, with their address and status.

Questions

API keys and tokens (GitHub, GitLab, Slack, Stripe, AWS, Google, OpenAI, Anthropic, npm), JWTs, Authorization headers, private keys, passwords in fields and in URLs, cookies, email addresses, IPv4 and IPv6 addresses, and the values in URL query strings. Each one becomes a placeholder like [TOKEN-1]. Local addresses such as 127.0.0.1 and version numbers stay.