Skip to main content
Kasava’s bug tracking system captures bugs with rich context including video recordings, screenshots, console logs, network requests, and user actions. AI analysis powered by Gemini then helps create detailed GitHub issues automatically.

How It Works

1

Capture

Use the Chrome extension to record bugs with video, audio narration, and automatic technical context capture
2

Analyze

AI analyzes the recording to identify the issue, determine severity, and extract key details
3

Create Issue

Generate a GitHub issue with full reproduction steps, technical data, and links to recordings
4

Share

Publish bug reports with shareable links for team collaboration or external stakeholders

Key Features

One-Click Recording

Start recording with a single click or keyboard shortcut. The extension captures:
  • Screen video with full resolution
  • Optional audio narration
  • Console logs (errors, warnings, info)
  • Network requests with timing data
  • User actions (clicks, inputs, navigation)
  • Page metadata and browser information

AI-Powered Analysis

After recording, Kasava’s AI automatically:
  • Confirms whether the issue is a bug
  • Identifies the root cause
  • Extracts step-by-step reproduction instructions
  • Assigns severity level (critical, high, medium, low)
  • Suggests actions for resolution
  • Provides confidence scores for analysis

Smart Filtering

The extension intelligently filters out noise:
  • Analytics and tracking scripts (Google Analytics, Facebook Pixel, etc.)
  • Advertisement networks
  • Browser extension interference
  • Duplicate console messages
  • Development server notifications

GitHub Integration

Create GitHub issues directly from bug reports:
  • Auto-generated title and description
  • Embedded video recording link
  • Console error details
  • Network request failures
  • Browser and device information

Chrome Extension

The Kasava Chrome Bug Detector captures comprehensive bug context with one click.

Supported Browsers

The extension works with all Chromium-based browsers:
  • Google Chrome (v100+)
  • Microsoft Edge
  • Brave
  • Arc

Installation

1

Download the Extension

Go to Settings > Chrome Extension in Kasava and click Download for Chrome
2

Open Extensions Page

Navigate to chrome://extensions/ in your browser
3

Enable Developer Mode

Toggle Developer mode in the top-right corner of the extensions page
4

Install Extension

Drag and drop the downloaded file into the extensions page, or click Load unpacked and select the extracted folder
5

Pin to Toolbar

Click the puzzle piece icon in your toolbar and pin Kasava for easy access
6

Sign In

Click the Kasava icon and sign in with your Kasava account

Keyboard Shortcuts

ActionWindows/LinuxMac
Start/Stop RecordingCtrl+Shift+RCmd+Shift+R
Take ScreenshotCtrl+Shift+SCmd+Shift+S
Customize shortcuts at chrome://extensions/shortcuts.

Extension Settings

Access settings by right-clicking the extension icon and selecting Options.
SettingDescription
API KeyYour Kasava API key for authentication
Console TrackingEnable/disable console log capture
Network TrackingEnable/disable network request capture
Recording DurationMaximum recording length (default: 5 minutes)
Auto-AnalysisAutomatically analyze recordings after capture

Recording Bugs

Starting a Recording

1

Navigate to the Issue

Go to the page or state where the bug occurs
2

Start Recording

Click the Kasava extension icon or use Ctrl+Shift+R / Cmd+Shift+R
3

Reproduce the Bug

Demonstrate the issue while the extension captures everything automatically
4

Stop and Submit

Click stop, add a description, and submit the report

What Gets Captured

ComponentDescription
VideoScreen recording of the bug reproduction
AudioOptional voice narration explaining the issue
Console LogsJavaScript errors, warnings, and messages
NetworkHTTP requests with status codes and timing
User ActionsClicks, inputs, form submissions, navigation
MetadataURL, browser, OS, viewport, timestamp

Recording Best Practices

Do:
  • Show the bug clearly and completely
  • Narrate your actions for context
  • Include any error messages in frame
  • Mention how often the bug occurs
Don’t:
  • Record sensitive data (passwords, API keys)
  • Make recordings longer than necessary
  • Rush through complex reproductions

Viewing Reports

Navigate to Bug Reports in the sidebar to see all captured bugs.

Reports List

Each report shows:
InformationDescription
DescriptionBrief description of the bug
EnvironmentLocal, staging, or production
URLWhere the bug was captured
DeviceBrowser and operating system
IssuesCount of console errors and warnings
GitHubLink to associated GitHub issue

Report Detail View

The full detail view includes:
  • Video Tab: Watch and edit the recording
  • Console Tab: View captured console output filtered by log level
  • Network Tab: Review HTTP activity with failed requests highlighted
  • User Activity Tab: See the sequence of user interactions
  • AI Analysis: Summary, severity, root cause, reproduction steps, and suggested actions

Available Actions

  • Create GitHub Issue: Convert the bug report into a GitHub issue with pre-filled content
  • Generate Plan: Create a Plan from the bug report for larger feature work
  • Publish Report: Generate a shareable link with optional password protection

Use Cases

QA Testing

QA team members can quickly capture bugs during testing sessions without switching contexts. The AI generates reproduction steps automatically.

User Feedback

Share recording links with users or stakeholders. They can record issues and submit them directly without needing detailed technical knowledge.

Production Debugging

Capture production issues with full context for faster debugging. Console logs and network data help pinpoint the root cause quickly.

Troubleshooting

  • Verify you’re signed in by clicking the extension icon
  • Ensure the site is HTTPS (not HTTP)
  • Grant microphone/camera permission if prompted
  • Reload the page and try again
  • Verify console tracking is enabled in settings
  • Some sites with strict Content Security Policies block script injection
  • Verify network tracking is enabled
  • Review URL filter patterns for over-filtering
  • Service Worker requests may not be captured
  • Recordings have a maximum duration (default 5 minutes)
  • Cannot record chrome:// internal pages