diagnostic · one of 36 free, no counter
Console
What is this page saying to its console?
Pages talk: deprecation warnings, framework complaints, debug lines somebody shipped. All of it is said, never thrown, so none of it reaches an error handler - it is invisible unless the devtools console happened to be open when it happened. This installs a tap on the page's own console for exactly as long as you record, and hands back each distinct line with a count instead of a scrolling transcript.
Reach it Press ⌘ + K on any tab and type console. Ctrl + K on Windows and Linux
in the panel · free, no counter
What this actually is
what the page says to its console, warnings included, counted liveA library warning you suspect is firing on every keystroke, a deprecation notice that needs to be read before a browser release makes it an error, or a check that your own production build is not narrating its internals to anyone who opens devtools.
Asked about this diagnostic
4 of themHow is this different from Errors?
Said against thrown. A console.warn is a sentence the page chose to say and no error handler ever hears; an uncaught exception is a failure. Errors records the failures - this records the talking, which is where deprecations, framework warnings and leftover debug lines live.
Why does it miss lines from before I pressed record?
Because hearing a console line requires a tap on the page's own console, and the tap exists only between record and stop. Lines said before it are gone, and pretending otherwise would be a reading invented after the fact. Record first, then do the thing you are curious about.
What if a logged line contains a token or an email address?
It passes the same sanitizer as everything else read from a page - emails and token-shaped strings are redacted, long lines are cut - and nothing is kept once the panel closes or sent anywhere at any point.
Why does the recording hear nothing on some pages?
The tap is a main-world script, and some pages - and every browser-internal one - refuse main-world scripts. The tool says so directly, because a tap that could not be installed is not the same finding as a page with nothing to say.
how to use console
- Open Console and press record - the tap is installed then, and never before.
- Use the page: type in the field, open the menu, do whatever you suspect is noisy.
- Stop. Each distinct line is one row with a count, so a warning fired 400 times is still one row.
- Every line has been through the sanitizer, and nothing is kept once the panel closes.
70 of these · no host permissions · three free audits