betterConsole

About

betterConsole is a privacy-first debugging extension for Chrome, Microsoft Edge, Brave, and Chromium-based browsers. It helps developers inspect and organize console activity from the current browser tab, including console logs, warnings, errors, runtime exceptions, unhandled promise rejections, failed resource loads, and CSP violations, without replacing or breaking the browser’s native console behavior.

The extension groups repeated issues, highlights likely source files, detects framework-specific hints, provides practical fix suggestions, and gives developers a Vision Mode overview of the current page’s console health. By default, betterConsole follows the active tab only. Developers can enable an explicit all-tabs mode when they need a wider debugging view.

Clicking an issue opens an inline accordion with root-cause details, source and page context, solution steps, research links, developer notes, a clean report view, and stack trace details. Developers can pause or resume capture, refresh the active tab, clear current-tab logs, reset all logs, mark issues fixed, ignore noisy issues, add notes, copy clean error text, export issues, and generate sanitized Markdown debug reports for GitHub Issues, Jira, Linear, Slack, Discord, email, and pull request comments.

betterConsole stores captured debugging data locally in browser storage. Console output, stack traces, URLs, notes, and reports are not sent to a server by betterConsole. The extension does not collect analytics, does not sell data, does not inject advertising, and does not execute remote code.

Online fix search is user-controlled. When a developer chooses to search for a fix, betterConsole generates a sanitized search query, shows it for review, and opens a normal browser search tab only after the developer confirms the search. Developers should review the query before searching to avoid sharing sensitive project details.