Console Maven Widgets - Live Testing & Demo

Comprehensive Testing Environment + Marketing Demo

💡 Why Console Maven Widgets?

Real-time error tracking gives you visibility into what's actually happening in your users' browsers - not just your development environment. Console Maven captures errors as they occur, with full context, stack traces, and AI-powered fix suggestions.

⚡ Real-Time Capture

Automatically captures all console errors, warnings, and logs as they occur. No manual integration beyond the script tag.

📍 Stack Trace Analysis

Full stack traces with file names, line numbers, and column positions for precise debugging.

🤖 AI-Powered Suggestions

Get instant fix recommendations powered by AI for common errors (Pro tier).

📦 Installation (< 60 seconds)

<script src="https://console-maven-frontend.fly.dev/latest/console-maven.min.js"
        data-api-key="YOUR_API_KEY"
        data-auto-render="true"></script>

✓ Auto-initializes • ✓ DebugFooter appears automatically • ✓ Starts capturing errors immediately

🧪 Widget Testing Controls

Use the buttons below to render, test, and destroy each widget. Click Render to initialize a widget, then trigger some errors (see "Demo Actions" section) to see how each widget captures and displays them.

DebugFooter Widget Inactive

Toolbar Widget Inactive

StatsOverlay Widget Inactive

Agentic Assistant (ChatWidget) Inactive

Uses localhost:2007 for local testing

Demo Actions (Generate Test Data)

No logs yet. Click buttons above to generate test data.

Browser Warnings (Test ReportingObserver & BrowserWarningCapture)

Note: These buttons trigger real browser-generated warnings that Console Maven's BrowserWarningCapture will detect via ReportingObserver API. Check the browser console and Stats Widget to see them captured.

CSP Testing (Content Security Policy)

CSP Modes:
  • Disabled: No CSP headers sent. eval() works normally.
  • Report-Only: CSP violations are logged but not blocked. eval() works, but violations appear in console.
  • Enforcing: CSP violations are blocked. eval() will fail with CSP error.
Test: Change CSP mode, then run "Comprehensive Stress Test" to see how CSP errors are detected in the Stats Widget.