Welcome to bugAgent

We're thrilled to have you here! Dive in to learn how to give your AI agents their own bug reporting enrichment platform — along with a host of features and tools designed for the agentic era of software development.

bugAgent's mission is to 10x the velocity of testers by removing administration friction and letting them do what they do best — test in flow. Whether you're building autonomous coding assistants, integrating QA into CI/CD pipelines, or looking for a smarter way to manage bugs — you're in the right place.

Get Started

Jump into the area that fits your needs:

Why bugAgent? Our Philosophy

Context-driven testing. Measurable quality. Continuous improvement.

The Most Context-Aware Bug Reporting Platform

Every feature in bugAgent is designed to capture, preserve, and use context. Traditional bug trackers lose critical information at every handoff — between the tester who found the issue, the report that describes it, and the developer who fixes it. bugAgent eliminates those gaps by maintaining deep context across every touchpoint:

Quality of Testing = Quality of Product

bugAgent doesn't just track bugs — it actively measures and improves the quality of testing itself. The core thesis is simple: higher quality testing produces better bug reports, which leads to faster fixes and higher product quality.

The Continuous Improvement Loop

These capabilities create a virtuous cycle that raises product quality over time:

Measure testing quality → Identify gaps → Improve practices → Re-measure → Ship better software

Every report scored, every quality trend tracked, and every coverage gap identified feeds back into better testing practices. Teams using bugAgent don't just find more bugs — they get measurably better at finding them.

Introduction

Give AI agents a bug platform.

Software is increasingly written, tested, and maintained by AI agents. These agents need infrastructure — not just for writing code, but for the entire quality lifecycle. bugAgent is the platform that gives agents (and the humans who work alongside them) a shared language for bugs: one that's structured, enriched, and ready for action.

We built bugAgent because we believe the next generation of software teams will be hybrid — humans and agents collaborating in real-time. For that to work, bugs can't live in a spreadsheet or a GUI-first tracker. They need an API-first, protocol-native home where every participant (agent, human, CI pipeline, or IDE) can read, write, and act on them instantly.

What is bugAgent?

bugAgent is an API platform for giving AI agents their own bug reporting and product quality infrastructure. It goes beyond tracking — bugAgent is a report enrichment platform that classifies, contextualizes, and routes bugs, feature requests, enhancements, and more automatically.

With bugAgent, agents can:

• Manage reports autonomously — create, classify, query, update, and resolve bug reports, feature requests, enhancements, and more without human intervention. Each report includes a built-in timer you can start, stop, and resume to track exact testing time down to the second. Click the time display to manually adjust. The timer is available on both the creation form and the report detail page
• Enrich reports with AI — every report is auto-classified across 19 types — bugs (UI, performance, crash, security, logic, data, network, accessibility, compatibility), feature requests, enhancements, technical debt, documentation, DevOps, UX improvements, and integrations — with a confidence score
• Deploy human testers Coming Soon — request on-demand exploratory or Playwright automation testing from human QA teams
• Scan code and UI Coming Soon — run multi-agent swarms to check for abnormalities, vulnerabilities, and broken or outdated dependencies
• Sync to external tools — push enriched reports to Jira with mapped fields, priority, and labels. Playwright scripts auto-sync to GitHub repos via the GitHub integration
• AI Assistant — your QA command center — a context-aware assistant that goes far beyond report creation. Create and update bug reports, change status, severity, and type, add comments, create testing notes in 5 formats (Markdown, Plain Text, Checklist, Outline, Bug Template), list and search reports, notes, automations, and schedules, and send feedback — all through natural conversation. Use voice input powered by Whisper transcription, attach files, and let the AI analyze session replays to auto-draft reports. Start a new chat anytime with the New Chat button. Available in both the dashboard and the in-app FAB popup (no login required for FAB)
• bugAgent Tools (SDK) — the SDK captures the last 60 seconds of clicks, navigation, DOM mutations, errors, and network failures. Includes console log capture with full stack traces (last 50 entries), a network waterfall of failed and slow API requests, real-time performance metrics (page load, FCP, FPS, memory, long tasks), optional screen + voice recording via the FAB toolbar, DOM snapshot replay, and a browser markup/annotation tool for drawing circles, arrows, and freehand annotations on screenshots before submitting. Available on Pro and Team plans
• Quality Score — measure your testing — every report is scored 1–10 to measure the quality of the testing, not just the severity of the bug. The score evaluates 10 context-driven dimensions: reproduction steps, expected vs actual, environment details, evidence, root cause analysis, impact assessment, context & history, heuristics & oracles, clarity & structure, and actionability. Teams track their average score trending over time in Analytics, and the Quality Testing Health Score (0–100) gives leadership a single metric for testing effectiveness. Visual badges (red 1–3, amber 4–6, green 7–10) help teams identify weak reports before development starts. Available via dashboard, API, and MCP
• Detect duplicates automatically — when a new report is created, text similarity analysis compares titles and descriptions against existing reports in the same project, flagging potential duplicates with match scores and direct links
• Analytics Dashboard — a full-screen suite with 12+ interactive charts: Bug Reports Over Time (stacked bars by severity), Quality Score Trend (line chart), Severity/Status/Type breakdowns (donuts + bars), Top Bug Reporters leaderboard, Automation Health (pass/fail), Time Tracking by day and category, Notes Created sparkline, and Resolution Time. Includes a Quality Testing Health Score gauge (0–100) with crown icon on the best-performing area. Filter by time range (7/14/30/90 days) and project. Pro and Team plans. Also available via the REST API (GET /analytics) and MCP get_stats tool
• No-code web automation — record browser actions with zero code — AI generates production-ready Playwright scripts automatically. Run tests on virtual viewports (30+ emulated devices) or live real browsers via BrowserStack (Chrome, Firefox, Safari, Edge on Windows and macOS). End-to-end testing that builds, manages, and scales with your product. Toggle between Virtual and Live modes on each run or schedule. AI optimization powered by Sonnet 4. Scripts track up to 10 versions with one-click undo. Line-by-line pass/fail highlighting. Pro and Team plans include an automation coverage mind map on the dashboard
• Notes — capture testing observations in 5 formats (Markdown, Plain Text, Bug Template, Checklist, Outline). Includes voice-to-text dictation via OpenAI Whisper, a built-in timer you can start, stop, and resume to track exact testing time down to the second — click the time display to manually edit. Tracked time transfers automatically when converting a note to a bug report. Also includes file attachments up to 10 MB, private or shared visibility, auto-save, and keyword search with project, author, and date filters. Available on all plans
• Time Tracking — log daily QA effort with categories (testing, bug-triage, automation, review, meeting). Create, update, and delete time entries per project. Filter by period (today, week, month), category, and team member. View daily, weekly, and monthly summaries in the analytics dashboard. Available via dashboard, API, and MCP. Team and Enterprise plans
• Test Cases — a complete test management system inspired by TestRail. Create test cases with detailed steps (action + expected result) and drag-and-drop step reordering. Group them into test suites, create and assign test runs to team members with notifications, execute by marking each case pass/fail/blocked/skip with auto-save, instantly file bug reports from failures with full test context — bug reports link back to the test case and test run for full traceability. Re-run only failed cases, view reports with pass rate and date filtering, color-coded cards, and CSV export. Use Rapid Mode for fast test case creation. Available via dashboard, REST API, and MCP
• Geo-Snap — enter any URL and capture screenshots from 50+ countries simultaneously. Verify localized content (currency, language, regional pricing), test geo-redirects, monitor competitors across markets, and check compliance with local regulations like cookie banners and privacy notices. Free plan: 1 country at a time with 10 saved screenshots. Pro/Team: up to 5 countries simultaneously with unlimited saved screenshots. Available via dashboard, REST API, and MCP create_geo_snap tool
• Mobile Testing — upload APK (Android) or IPA (iOS) apps and run automated tests on real devices. Write Appium scripts for complex interactions or Maestro YAML for simple flows. Run on 3,000+ real devices via BrowserStack and Maestro Cloud. Every run produces video recordings, screenshots, device logs, and performance metrics. Failures auto-create bug reports with all artifacts. Schedule runs on multiple devices with Slack/email notifications. Device matrix testing across OS versions. Free: 1 run/day, Pro: unlimited, Team: unlimited. Available via dashboard, REST API, and MCP tools
• Performance testing — Page quality audits (Performance, Accessibility, Best Practices, SEO) combined with load testing using virtual users (RPS, latency percentiles p50/p90/p95/p99). Mobile app performance testing on real Android/iOS devices via BrowserStack App Profiling — track CPU, memory, FPS, battery drain, and launch time with a Web/Mobile toggle. Core Web Vitals tracking, auto-bug creation when thresholds are breached (web scores or mobile metrics) with screenshot, recommendations, diagnostics, and quality scoring. CSV report export and archive/unarchive runs. Pro/Team/Enterprise plans
• Security scanning — OWASP ZAP + Nuclei web DAST, MobSF mobile binary analysis, and Semgrep code SAST. Findings categorized by severity (Critical, High, Medium, Low, Info) with CVSS scores, CWE IDs, and remediation guidance. Auto-creates security bug reports for Critical/High findings. Pro/Team/Enterprise plans
• Kanban Board — visualize bug reports across 8 status columns (New, Awaiting Triage, Confirmed, In Progress, Resolved, Retesting, Closed, Reopened) with drag-and-drop status management. Dragging a card updates the status in real time and syncs bi-directionally to Jira instantly. Toggle between list and kanban views with a persistent preference. Each card displays severity, type, description preview, and timestamps
• Team Booster — scale your QA team instantly with pre-configured tester accounts. Fill in team size (1–10), location, duration, technical level, and budget — accounts are created in seconds and testers appear in your Team Management page with full platform access. Available on Pro and Team plans. You will not be charged until approval has been given. Also available programmatically via the REST API (POST /team-booster) and the MCP scale_team tool

This allows agents to assume their own identity and communicate via the universal protocol of bugs — with services, people, and other agents across any IDE or platform.

<script src="https://app.bugagent.com/sdk/bugagent-sdk.js" data-key="YOUR_API_KEY" data-position="bottom-right"></script>

What can autonomous agents do on this platform?

bugAgent gives autonomous agents the same access as the AI Assistant — every feature is available through the REST API and Model Context Protocol. Agents can file bugs, read reports, trigger tests, analyze results, update statuses, and orchestrate entire QA workflows without human intervention. Here are real-world autonomous cycles that agents can run on the platform:

The Problem

Traditional bug management systems were built for humans clicking through web interfaces. They assume someone will manually fill out a form, pick a category from a dropdown, assign a priority, and tag the right team. This model breaks down in the age of AI-assisted development:

The Agentic Development Cycle

Software development is shifting from a human-only process to a collaborative cycle between humans and agents. In this new paradigm, AI agents write code, review pull requests, run tests, and monitor production — all alongside human developers.

A QA AI Agent fits naturally into this cycle as the quality layer — continuously scanning for issues, filing enriched bug reports, and coordinating fixes. But for this to work, the QA agent needs a platform that speaks its language: structured data over APIs, machine-readable classifications, and protocol-native communication.

bugAgent is that platform. It sits at the intersection where agents, humans, and tools converge — providing a universal protocol for quality that works across any IDE, CI system, or communication platform.

The Solution

bugAgent is an API-first bug enrichment platform designed for agents. Every feature, from report creation to Jira sync, is available through structured APIs and the Model Context Protocol — not locked behind a web UI.

API-First Infrastructure

What does API-first mean for a bug management platform?

AI-Native Features

bugAgent doesn't just store bugs — it understands them:

Claude Integration

Self-healing bug analysis powered by Anthropic.

Connect your Anthropic API key to push bug reports to Claude for root cause analysis and fix suggestions. Claude analyzes each report and returns actionable insights including likely causes, affected areas, and recommended fixes. Available on Pro and Team plans.

How to Connect

Navigate to Settings → Integrations in the dashboard. In the Claude by Anthropic section, enter your Anthropic API key (starts with sk-ant-) and select your preferred model (Claude Sonnet 4, Claude Opus 4, or Claude Haiku 3.5). Click Connect to save.

Per-Project Configuration

Once connected, configure Claude on a per-project basis:

• Auto-push bugs to Claude — toggle this on to automatically send every new bug report to Claude for analysis as soon as it's created
• Custom instructions — add project-specific context such as your tech stack, architecture patterns, or areas of focus (up to 5,000 characters). Claude uses these instructions to provide more relevant analysis

Manual Analysis

From any bug report detail page, click Send to Claude to push the report for analysis on demand. If an analysis already exists, click Re-analyze to get a fresh evaluation. The analysis appears inline on the report page with formatted root cause details and fix suggestions.

API and MCP Access

Claude analysis is available through multiple interfaces:

• REST API — call POST /api/claude/push with a report_id to trigger analysis programmatically. The response includes the full analysis text and timestamp. See the API reference for details.
• MCP tool — use the push_to_claude tool from any MCP client (Claude Desktop, Cursor, VS Code, Claude Code). Pass a report_id and receive the analysis directly in your AI workflow. See the MCP documentation.
• Dashboard — click Send to Claude on any bug report detail page for on-demand analysis with a visual interface.

The Self-Healing Cycle

bugAgent as the orchestration layer for autonomous software quality.

bugAgent connects QA, development, and AI into one continuous improvement cycle. When all components are active, software effectively heals itself — with humans reviewing and guiding every step.

1. Record — Capture Issues From Every Source

Issues enter the system through multiple channels, each producing structured, enriched bug reports:

• FAB tools (SDK) — the floating action button captures DOM recordings, console logs, network waterfalls, performance metrics, and screenshots directly from the browser. The AI auto-drafts bug reports from session data.
• Playwright automation — scheduled and on-demand test scripts detect regressions and failures automatically. Failed runs generate bug reports with video evidence and error details.
• AI assistant — the dashboard and in-app AI assistant lets team members create detailed bug reports through natural conversation, including voice input and file attachments. Also supports triggering web and mobile performance tests, listing runs, and reviewing results.
• MCP agents — AI agents running in Claude Desktop, Cursor, VS Code, or Claude Code file bug reports directly through the Model Context Protocol. CI/CD agents can report issues as part of the pipeline.
• Email — send bugs via email and they are automatically classified, filed, and synced to your project tracker.

2. Diagnose — Claude Analyzes Root Cause

Once a bug report exists, Claude can analyze it to determine the probable root cause and suggest a fix:

• Auto-push — enable per-project to automatically send every new bug report to Claude the moment it is created
• Manual push — click Send to Claude from the dashboard, or use push_to_claude via MCP, or call POST /api/claude/push via REST API
• Structured analysis — Claude returns probable cause, affected areas, a suggested fix with code-level specifics, verification steps, and a risk assessment
• Custom instructions — per-project context (tech stack, architecture, focus areas) makes analysis more accurate and relevant

3. Automate — Verify Fixes Continuously

Playwright automation scripts provide the verification backbone:

• Scheduled runs — tests run on a cron schedule to catch regressions before users do
• On-demand runs — trigger tests via the dashboard, API, or MCP after applying a fix
• 30+ device targets — run tests on desktops, laptops, iPhones, Android phones, and tablets. Select the device when triggering manual or scheduled runs
• AI optimization — send any script to Sonnet 4 for a 12-point optimization that fixes selectors, wait strategies, assertions, error handling, auth patterns, mobile compatibility, and strict mode issues
• Version history & undo — every script tracks up to 10 previous versions. One-click undo reverts to the prior version. Versions are saved before manual edits, AI optimization, and script regeneration
• Line-by-line results — after a run completes, the script highlights passed lines in green and failed lines in red so you can see exactly which step broke
• CI/CD integration — run tests as part of your deployment pipeline and auto-file bugs on failures
• Video evidence — every run produces video results so teams can see exactly what happened

4. Heal — AI Agents Close the Loop

Connected AI systems can read Claude's analysis and act on it autonomously:

• Read analysis via MCP — agents call get_bug_report to retrieve the Claude analysis including root cause and suggested fix
• Apply fixes — coding agents (Claude Code, Cursor, custom agents) read the suggested fix and apply code changes directly
• Trigger re-verification — after applying a fix, agents call run_automation to trigger the relevant Playwright tests
• Update status — agents update the bug report status and add comments documenting what was changed and verified

5. Human in the Loop — Review, Approve, Guide

Humans remain essential at every stage of the cycle:

• Review — teams review Claude's analysis and AI-applied fixes before merging to production
• Approve — pull request reviews, test result sign-offs, and deployment approvals keep humans in control
• Guide — custom instructions, project configuration, and priority settings direct how the system behaves
• Override — any automated action can be paused, reversed, or manually corrected at any time

The Full Picture

When all components are connected, bugAgent becomes the orchestration layer for a full-circle autonomous QA pipeline:

Record → Diagnose → Automate → Heal → Record …

Each cycle produces better software. Bugs are caught earlier, fixes are more targeted, regressions are detected faster, and the AI learns from project-specific context. Teams spend less time on triage and more time building features — while bugAgent orchestrates the quality lifecycle around them.

bugAgent Skills

Integrations that connect external tools directly into bugAgent's context engine.

Skills are first-class integrations that plug external services into bugAgent. Each Skill enriches the context engine with data from tools your team already uses — syncing repositories, pulling analysis, bridging issue trackers, and more. Once enabled, Skills operate automatically in the background, keeping your QA data connected and up to date.

Available Skills

How to Enable Skills

Navigate to Settings → Integrations in the dashboard. Each Skill has its own connection flow — OAuth for GitHub and Jira, API key for Claude. Once connected, configure per-project settings such as auto-push, repository mapping, or default Jira project.

Building Custom Skills

Partners and developers can build their own Skills to extend bugAgent. Custom Skills connect external tools via OAuth or API keys, feeding data into the context engine alongside the built-in integrations.

• Submit an integration — reach out via the homepage or email support@bugagent.com to propose a new Skill
• Build programmatically — use the API reference to build Skills that interact with bugAgent endpoints for reports, automation, and project data

Free Migration

Switch to bugAgent with zero friction — we handle the heavy lifting.

Moving from another bug tracking or QA tool? The bugAgent team will migrate your data for free. We export your existing bug reports, test scripts, and project configuration, then import everything into your new bugAgent workspace.

What's Included

• Bug report export — we export your existing bug reports from your current tool and import them into bugAgent with full metadata preserved
• Playwright automation scripts — we walk you through creating Playwright automation scripts tailored to your product's test scenarios
• Integration configuration — we help you connect Jira, GitHub, Slack, and Claude so your workflow is fully operational from day one
• Team onboarding — we set up your team accounts, projects, and permissions to match your existing structure

Dedicated QA Team

Professional QA engineers embedded in your workflow.

For teams that want hands-on support, bugAgent offers a dedicated QA team service. Our professional QA engineers work directly inside your bugAgent workspace to review, enrich, and act on your bug reports.

What the QA Team Does

• Bug report review and enrichment — our QA engineers review incoming reports, add reproduction steps, verify severity, and ensure every bug meets a high quality bar before it reaches your developers
• Automation script development — we develop Playwright automation scripts for your product, covering critical user flows, regression scenarios, and edge cases
• Custom features and integrations — need a custom Skill, a bespoke reporting dashboard, or a CI/CD pipeline integration? Our team builds it for you
• Ongoing QA operations — continuous testing, triage, and quality monitoring tailored to your release cadence and priorities

Test Cases

bugAgent includes a complete test case management system inspired by TestRail, built for modern QA teams. Manage your entire testing lifecycle from case creation to execution reports.

Core Concepts

• Test Cases — individual test scenarios with a name, description, preconditions, and ordered steps. Each step has an action (what to do) and an expected result (what should happen). Drag-and-drop step reordering lets you reorganize steps without recreating them. Cases include priority (critical, high, medium, low), type (functional, regression, smoke, integration, e2e, performance, security, usability, accessibility), tags, and estimated execution time. Use Rapid Mode for fast test case creation when you need to build a large suite quickly
• Test Suites — collections of related test cases. Suites let you organize cases by feature, sprint, or any grouping. Each suite tracks its case count and last run status. Color-coded cards help you see suite health at a glance
• Test Runs — an execution session created from a suite. When you create a run, all cases from the suite are snapshotted at that point in time. Assign runs to team members with notifications and track progress as each case is marked pass, fail, blocked, or skip with auto-save
• Test Reports — aggregated results from completed runs with pass rate, date range filtering, per-suite breakdowns, color-coded cards, and CSV export

Workflow

1. Create test cases with detailed steps describing the action and expected result
2. Group related cases into test suites (e.g. "Checkout Regression", "Login Smoke Tests")
3. Create a test run from a suite and assign it to a team member with notifications
4. Execute the run: mark each case as passed, failed, blocked, or skipped with notes — results auto-save
5. When a case fails, instantly create a bug report with full context from the test case — the bug report links back to the test case and test run
6. Re-run only the failed cases after fixes are deployed
7. Review reports with pass rates and trends over time, export to CSV

Full Traceability

Every bug report traces back to its origin: manual testing, automation failure, test case run, AI assistant, or FAB SDK. The entire QA lifecycle is connected:

• Test case runs link to bug reports — when a case fails and you create a bug report, the report includes full context: test case name, steps, expected vs actual, and the test run it came from
• Bug reports link to test cases and automation scripts — every bug report shows its origin, whether it was filed from a test run, an automation failure, the AI assistant, or the SDK
• Automation failures create linked bug reports — when a Playwright script fails, the generated bug report links back to the automation script with line-by-line results
• End-to-end chain — test case → test run → bug report → fix → re-test. No broken chains, no lost context

Access

Test Cases are available through the dashboard, the REST API (full CRUD for cases, suites, runs, and reports), and the MCP server (7 tools for AI agent integration). Duplicate cases with one click, reorder cases within suites via drag-and-drop, and filter by priority, type, status, and tags.

Geo-Snap

Geo-Snap lets you enter any URL and capture screenshots of how a website appears from 50+ countries simultaneously. Powered by real geo-IP routing, every screenshot shows exactly what a visitor in that country would see — including localized content, regional pricing, language variants, and geo-specific redirects.

How It Works

1. Enter a URL — paste any public website address into the Geo-Snap input
2. Select countries — choose from 50+ countries (United States, United Kingdom, Germany, Japan, Brazil, Australia, and many more)
3. Capture — screenshots are taken from real IP addresses in each selected country and delivered within seconds

Key Use Cases

• Localization verification — confirm that currency, language, date formats, and regional content display correctly for each market
• Geo-redirect testing — verify that visitors are redirected to the correct regional version of your site (e.g., .co.uk, .de, .jp)
• Compliance checks — ensure cookie consent banners, GDPR notices, and other regulatory requirements appear in the correct regions
• Competitive monitoring — see how competitor websites look and price products across different markets

Plan Limits

Access

Geo-Snap is available through the dashboard, the REST API (list, create, delete), and the MCP server (create_geo_snap tool for AI agent integration).

Mobile Testing

Mobile Testing lets you upload APK (Android) or IPA (iOS) apps and run automated tests on real BrowserStack devices — Pixel, Galaxy, iPhone, iPad, and more. Record test actions in-browser and let AI generate production-grade scripts, or write your own. Every run produces video recordings, Appium logs, device logs, and network logs. Failed runs automatically create comprehensive bug reports with failure snapshots and step breakdowns.

Record & Generate Scripts

Walk through your app on a virtual device directly in the browser. Log tap, swipe, input, and back actions as you go. When you stop recording, AI (Claude Sonnet 4) generates three production-grade scripts simultaneously:

Save any script as an automation and run it on real devices immediately.

Supported Platforms

• Android — upload .apk files. Works directly for both recording and running on real devices (Pixel, Galaxy, OnePlus, Xiaomi).
• iOS — upload .ipa files for running tests on real iPhones and iPads. For recording, also upload a simulator build (.app zipped) — build from Xcode targeting “iPhone Simulator” and zip the .app bundle.

Update App Version

Replace your app binary with a new version without creating a new entry. Click Update App on the app detail page and upload the new APK or IPA. The old file is automatically deleted from storage to save space, and all linked automations and scheduled runs will use the new version on the next execution — no reconfiguration needed. For iOS apps, replacing the IPA also removes the simulator build — you’ll need to re-upload the updated simulator .app to continue recording.

Run on Real Devices

Click Run Now on any automation to launch it on a real BrowserStack device. Select from popular Android and iOS devices — the dropdown automatically filters by your app’s platform. All script types (YAML, Appium Python, Appium JS) run through BrowserStack’s real device farm via the Appium 2.x W3C WebDriver protocol.

Run Detail Page

• Real-time polling — status auto-updates every 10 seconds while the test is queued or running, with a spinner banner
• Video recording — watch the full test execution on the device
• Searchable logs — Appium logs, device logs, and network logs with text search and match highlighting
• Duration, started, completed timestamps
• Rerun — one-click rerun with the same device and automation
• Archive — archive completed runs to keep the list clean. View archived runs with the status filter

Bug Reports from Failures

When a mobile test fails or errors, bugAgent automatically creates a detailed bug report including:

• Error message in a code block
• Test step breakdown with pass/fail icons and counts (e.g. “3/5 passed”)
• Device, platform, OS version in an environment table
• Failure snapshot as the first attachment (last screenshot = failure state)
• Video recording of the full run
• Full logs in a collapsible section (up to 5,000 characters)

The bug report links back to the run detail page and the automation. The run listing shows a red “Bug Report” link for failed runs.

Mobile Analytics

The Analytics dashboard includes a Mobile Testing row showing: total runs, pass/fail rate donut, runs by device bar chart, and Android/iOS platform split. Visible when you have mobile run data.

Scheduling & Notifications

Schedule mobile test runs using cron expressions with timezone support. Configure Slack or email notifications on failure so your team is alerted immediately when regressions are detected.

Plan Limits

Setup

Configure your BrowserStack credentials (BROWSERSTACK_USERNAME and BROWSERSTACK_ACCESS_KEY) in your environment. Upload apps and create automations via the dashboard, REST API, or MCP tools (upload_mobile_app, create_mobile_automation, run_mobile_test, list_mobile_runs).

Security & Two-Factor Authentication

bugAgent supports two-factor authentication (2FA) for all email/password accounts. Users can enable 2FA from Settings → Security to add an extra layer of protection to their account.

Supported Methods

How It Works

1. Enable: Go to Settings → Security → choose Authenticator App or SMS → scan QR code or enter phone number → verify with 6-digit code.
2. Login: Enter email + password → redirected to 2FA verification page → enter code from your app or SMS → access granted.
3. Google OAuth: 2FA is skipped entirely. Google manages security for OAuth users.
4. Disable: Settings → Security → Disable Two-Factor Authentication.

Verification Page

The 2FA verification page at login features a 6-digit code input with auto-advance between digits, paste support, and auto-submit when all 6 digits are entered. If both methods are enrolled, users can switch between “Use SMS instead” and “Use authenticator app instead.”

Middleware Protection

The dashboard middleware checks the Authenticator Assurance Level (AAL) on every request. If a user has 2FA enabled but hasn’t completed AAL2 verification, they are automatically redirected to the verification page. This prevents bypassing 2FA by navigating directly to dashboard URLs.

Storage Security

Organization storage usage is tracked at the team level. When usage reaches 80%, an amber warning banner appears across all dashboard pages. At 100%, a red banner indicates uploads are blocked. Contact hello@bugagent.com to increase storage limits.

Enterprise Security

Enterprise plan includes SSO/SAML, audit logs, on-premise deployment option, and multiple organization support. Contact sales for custom security requirements.

Analytics Dashboard

The Analytics Dashboard is a full-screen, interactive reporting suite available on Pro and Team plans. It provides real-time visibility into your team's testing health, bug trends, and QA performance across every project.

Quality Testing Health Score

At the top of the dashboard, a large gauge displays your overall Quality Testing Health Score from 0 to 100. This score is computed from four equally weighted components:

The component with the highest individual score displays a crown icon, highlighting your team's best-performing area at a glance.

Chart Sections

Below the health score, the dashboard includes 12+ interactive chart sections, each providing a different lens on your QA data:

Filtering & Controls

Every chart responds to two global filters at the top of the dashboard:

• Time Range — select 7, 14, 30, or 90 days. All charts, the health score, and the leaderboard update instantly
• Project Filter — scope the entire dashboard to a single project, or view aggregated data across all projects

API Access

All analytics data is available programmatically:

• REST API — GET /analytics returns daily counts, severity/status/type breakdowns, and health score. See the API Reference for parameters and response format
• MCP — the get_stats tool returns the same data for AI agents. Pass a days parameter (up to 90) to control the lookback window

Why bugAgent?

Here's why teams and developers choose bugAgent:

Developer Resources

Everything you need to build with bugAgent:

Frequently Asked Questions

Quick answers to the most common questions about bugAgent.

Support

We're here to help you build with bugAgent. Reach out anytime: