Skip to main content
โ† Back to Home

๐ŸฆŸ Mosqit Tutorial

Get started in 5 minutes

1

๐Ÿ“ฅ Install the Extension

Load the Mosqit extension in Chrome to start debugging with AI-powered insights.

Quick Install Steps:

  1. Open chrome://extensions/ in Chrome
  2. Enable "Developer mode" (top right)
  3. Click "Load unpacked"
  4. Select the dist/extension folder
โœ… Success! You should see the Mosqit icon (๐ŸฆŸ) in your Chrome toolbar.
2

๐Ÿค– Enable Chrome AI (Optional)

Get intelligent error analysis powered by Chrome's built-in AI (Gemini Nano).

AI Setup (2 minutes):

  1. Open chrome://flags in a new tab
  2. Search for: Prompt API for Gemini Nano
  3. Set it to: "Enabled"
  4. Search for: Gemini Nano
  5. Set it to: "Enabled"
  6. Restart Chrome completely

Test AI is working:

// Open Console (F12) and run:
await ai.languageModel.create();
// Should return: LanguageModel object
โš ๏ธ Note: AI features work without this, but you'll get pattern-based analysis instead of AI insights.
3

๐Ÿ”ง Open Mosqit DevTools

Access the Mosqit panel to start seeing intelligent error insights.

Open the Panel:

  1. Visit any website (try example.com)
  2. Press F12 or right-click โ†’ "Inspect"
  3. Look for the "Mosqit" tab in DevTools
  4. Click it to open the panel
๐Ÿ’ก Pro Tip: Keep DevTools docked to the bottom or right for the best experience.
4

๐Ÿงช Test with Real Errors

Trigger some errors to see Mosqit's AI analysis in action.

Try these in the Console:

// Null reference error
const user = null;
console.log(user.name);

// Undefined function
someFunction();

// Type error
const num = 5;
num.toUppercase();

What You'll See:

  • ๐Ÿค” "AI is analyzing..." indicator appears
  • โœจ AI-powered analysis with fix suggestions (1-2 seconds)
  • ๐Ÿ“ File location and line number
  • ๐ŸŽฏ Smart context about what went wrong
5

๐Ÿ› Visual Bug Reporter

Report visual bugs by clicking elements directly on the page. Captures screenshots, context, and element details automatically.

How to Use Visual Bug Reporter:

  1. In Mosqit DevTools panel, find the ๐Ÿ› Visual Bug Reporter button (toolbar, top right)
  2. Click it to switch from Logs view to Visual Bug Reporter view
  3. Click the "Start Capture Mode" button
  4. Hover over any element on the page (you'll see blue highlighting)
  5. Click the element you want to report

What Gets Captured:

  • ๐Ÿ“ธ Screenshot - Visual snapshot of the element and surrounding area
  • ๐ŸŽฏ Element Selector - CSS selector, XPath, and DOM position
  • ๐ŸŽจ Computed Styles - Colors, fonts, dimensions, spacing
  • ๐Ÿ“ Context - Page URL, viewport size, browser info
  • ๐Ÿ” Element Tree - Parent and child elements hierarchy
๐Ÿ’ก Pro Tip: Use this for reporting UI bugs like misaligned elements, wrong colors, missing images, or layout issues. The captured data is perfect for bug reports!
โš ๏ธ Note: After capturing, you can add annotations and submit directly to GitHub if configured. All data is session-only (ephemeral).
6

โšก Key Features

Quick overview of what makes Mosqit powerful.

๐ŸŽฏ

Smart Capture

Automatically captures console.error(), console.warn(), and uncaught exceptions

โœจ

AI Analysis

Chrome's Gemini Nano analyzes errors and suggests fixes instantly

๐Ÿ”

Pattern Detection

Identifies recurring errors and common patterns

โšก

Zero Persistence

Ephemeral like native console - no data left behind

๐ŸŽจ

Visual Inspector

Click any element to capture screenshots and context

๐Ÿ”’

Privacy First

All processing happens locally - nothing sent to servers

6

๐Ÿ’ก Pro Tips

Get the most out of Mosqit with these tips.

๐ŸŽฏ Filter by Level: Click error/warn/info buttons to filter logs
๐Ÿ” Search: Use the search bar to find specific errors quickly
๐Ÿ“‹ Copy Issues: Click any log to copy formatted error details
๐Ÿงน Clear Logs: Hit the clear button to start fresh (just like native console)
โš™๏ธ Debug Mode: Set DEBUG = true in source files to see internal logs

๐Ÿ“š Quick Reference

Keyboard Shortcuts

  • F12 - Open DevTools
  • Ctrl/Cmd + K - Clear console
  • Ctrl/Cmd + F - Search logs

Panel Controls

  • ๐Ÿ—‘๏ธ Clear - Clear all logs
  • ๐Ÿ”„ Filters - Toggle log levels
  • ๐Ÿ” Search - Find specific errors