Bug Reporting

Bug Reporting lets you record bug reproduction sessions with full context. Capture console logs, network requests, user interactions, and even backend server logs - giving AI everything it needs to understand and fix the issue.

Overview

When you record a bug:

  • All console output is captured (logs, warnings, errors)
  • Network requests are logged with status codes
  • User interactions are tracked (clicks, inputs)
  • Optional backend logs are included (via pointa dev)

This creates a detailed timeline AI can use to investigate and fix the bug.

Starting a Bug Recording

  1. Open the Pointa sidebar
  2. Click the Report Issue button
  3. A recording indicator appears showing elapsed time (max 30 seconds)
  4. Reproduce the bug in your application

What Gets Captured

Console Output

All console methods are captured:

  • console.log() - Regular logs
  • console.warn() - Warnings
  • console.error() - Errors with stack traces
  • console.info() - Info messages
  • console.debug() - Debug messages

Network Requests

For each request, Pointa captures:

  • HTTP method (GET, POST, etc.)
  • Request URL
  • Response status code
  • Timing information
  • Whether the request failed

User Interactions

Track what actions led to the bug:

  • Click events (with element info)
  • Input events (typing)
  • Scroll events
  • Page navigation

Screenshots

Pointa takes automatic screenshots:

  • At the start of recording
  • At the end of recording
  • Capturing the state before and after the bug

Backend Logs (Optional)

For full-stack debugging, you can capture server-side logs too by running your dev server via pointa dev:

npx pointa-server dev npm run dev

Now when you record a bug, your server's console output is automatically included in the timeline.

See Backend Logging Integration for detailed setup instructions.

Stopping and Submitting

When you've reproduced the bug:

  1. Click Stop Recording in the sidebar
  2. A form appears to describe the bug
  3. Add a title and description
  4. Optionally attach a screenshot
  5. Click Submit

Bug Report Timeline

The bug report includes a chronological timeline of all captured events:

00:00 - [Recording started]
00:01 - [Console] Fetching user data...
00:02 - [Network] GET /api/users → 200 OK
00:03 - [Click] Button.submit-btn
00:04 - [Console Error] TypeError: Cannot read property 'name' of undefined
00:04 - [Network] POST /api/submit → 500 Error
00:05 - [Recording stopped]

Bug Report Lifecycle

Status What It Means What Happens
Active New bug report, needs investigation AI investigates the timeline
Debugging AI added logging, needs re-run You reproduce bug again to capture new logs
In Review AI implemented a fix You test the fix
Resolved Bug is fixed Report is archived

When AI Needs More Information

Sometimes AI can't find the root cause from the initial recording. It may:

  1. Add debug logging to your code
  2. Mark the bug as "needs rerun"
  3. Ask you to reproduce the bug again

The new recording will include the extra logging, helping AI pinpoint the issue.

Tips for Bug Reporting

Clear Steps to Reproduce

Before recording:

  1. Know exactly how to trigger the bug
  2. Start from a clean state (refresh the page)
  3. Record the minimal steps needed

Be Ready to Describe

After stopping:

  • Note what you expected to happen
  • Note what actually happened
  • Mention if it's intermittent or consistent

Include Environment Details

If relevant, mention:

  • Browser version
  • Screen size / responsive issues
  • User state (logged in, specific account)

Viewing Bug Reports

All bug reports appear in the Pointa sidebar:

  • Click on any report to view details
  • See the full timeline
  • Read AI's analysis and fixes

Related Features