bugAgent

classify_bug

Classify a bug description into a bug type (ui, performance, crash, security, logic, data, network) with confidence score.

get_usage

Check current usage against plan limits. Shows reports used and remaining quota for your plan period.

sync_to_jira

Sync a bug report to Jira. Creates a Jira issue with mapped fields, labels, and priority. Requires a connected Jira account.

push_to_claude

Generate (or regenerate) the Developer Notes for a bug report — root cause, affected areas, suggested fix, verification steps, and risk assessment. Internally runs a multi-step chain that adapts to severity: medium/low bugs get a three-step chain (Sonnet draft → OpenAI challenger critique → Sonnet synthesis); critical/high bugs escalate to a five-step debate (draft → critique → Sonnet rebuttal → adjudicator, where a different model — default Claude Opus — reads the full transcript and writes the final notes with independent judgment). The response exposes every round (draft, critique, rebuttal, challenger_model, adjudicator_model, debated flag) so agents can inspect the reasoning chain. Any step failing falls through to the next-best answer. Uses platform keys — no per-team Claude connection required. Auto-fires on bug creation. Accepts UUID or short ID (PREFIX-NNN).

analyze_fix_area

Generate (or regenerate) the "Likely Fix Area" for a bug report — a narrow Sonnet output that names where in the codebase the fix most likely belongs. Uses the platform Anthropic key (no per-team Claude connection required). When the project has a GitHub repo mapped and the team has a github_connections row, the output is grounded in real file snippets; otherwise it falls back to general guidance with a nudge to connect a repo. Writes the result back onto bug_reports (likely_fix_area, likely_fix_area_status, likely_fix_area_generated_at) so the dashboard picks it up automatically. Accepts UUID or short ID (PREFIX-NNN).

list_projects

List available projects for the current user. Returns project names, slugs, and which is the default. Use a project slug with create_bug_report to file bugs into a specific project.

get_stats

Get bug report statistics: daily counts, breakdowns by type/severity/status. Use to answer questions like "how many bugs yesterday?" or "what types of bugs are most common?"

upgrade_plan

Upgrade your bugAgent subscription plan. Returns a Stripe checkout URL for the user to complete payment. After upgrading, use get_usage to confirm the new plan is active.

register_account

Create a new bugAgent account with email and password. The account is auto-confirmed and ready to use immediately. Returns user_id and email.

login

Sign in to bugAgent with email and password. Returns access tokens. In stdio mode, credentials are saved to ~/.bugagent/credentials.json for future sessions.

update_profile

Update your display name.

change_password

Change your account password.

get_settings

Get your profile info, plan, and notification preferences.

update_settings

Update notification preferences.

create_project

Create a new project. The first project becomes the default. Enforces plan limits.

delete_project

Delete a project. Choose how to handle its bug reports: move to another project, unassign, or delete them. All other project data (automations, test cases, mobile apps, schedules, geo snaps, notes, time entries) is permanently deleted. Only owner/manager can delete. Cannot delete last project.

create_performance_test

Create a performance test configuration. Combines Lighthouse page audits with k6 Cloud load testing. Enterprise only.

list_performance_tests

List performance test configurations for the current team.

run_performance_test

Run a Lighthouse + k6 Cloud performance test. Triggers a page audit and optional load test. Results include Core Web Vitals, performance scores, and load test metrics. Auto-creates bug reports when thresholds are breached.

get_performance_results

Get results for a performance test run. Includes Lighthouse scores (Performance, Accessibility, Best Practices, SEO), Core Web Vitals (LCP, FID, CLS, FCP, TTFB, INP, TBT, SI), and load test metrics (VUs, requests, RPS, p50/p90/p95/p99 latencies).

get_performance_usage

Check monthly performance test usage against plan limits. Performance testing is Enterprise-only. Limits: Free=0, Team=0, Enterprise=unlimited, Admin=unlimited.

create_security_scan

Create a security scan configuration. Web: Quick Scanner + Nuclei + ZAP DAST. Mobile: MobSF binary analysis for APK/IPA. Code: Semgrep SAST for 30+ languages. Configurable auto-bug creation with severity threshold. Enterprise only.

list_security_scans

List security scan configurations for the current team. Returns scan names, types, targets, and status.

run_security_scan

Trigger a security scan run. Web: Quick Scanner + Nuclei + ZAP. Mobile: MobSF binary analysis. Code: Semgrep SAST. Returns a run ID to poll for results.

get_security_results

Get results for a security scan run. Includes findings categorized by severity (Critical, High, Medium, Low, Info) with vulnerability type, description, affected URL/file, and remediation guidance.

get_security_usage

Check monthly security scan usage against plan limits. Security scanning is Enterprise-only. Limits: Enterprise=unlimited, Admin=unlimited.

list_code_reviews

List recent AI code reviews for the team. Returns review ID, repo, PR number/title, quality score, severity counts, and timestamps. Enterprise only.

get_code_review

Get a code review with all findings. Each finding includes severity, category (bug/security/performance/style/logic/maintainability), title, description, code suggestion, file path, and line numbers.

get_code_review_usage

Check monthly code review usage. AI code review is Enterprise-only. Enterprise: unlimited. Free and Team: 0.

get_code_review_analytics

Get code review analytics: trends, finding categories/sources, severity breakdown, velocity metrics, top repos, top authors. Enterprise only.

list_explorations

List Exploratory AI configs for the team. Each exploration targets a URL and can be run to autonomously find bugs.

create_exploration

Create a new Exploratory AI config. The exploration will autonomously crawl the target URL, generate test scripts, execute them, and file bug reports for issues found. Enterprise only.

get_exploration

Get an exploration config with its recent runs.

get_exploration_run

Get results of an exploration run including all findings, phase data, and linked bugs.

get_exploration_usage

Check monthly Exploratory AI usage. Exploratory AI is Enterprise-only. Enterprise: unlimited.

flush_reports

Bulk delete old bug reports. Only team owners and admins can flush. Optionally limit to a specific project.

generate_api_key

Create a named API key. The full key is returned only once — save it securely.

list_api_keys

List your active API keys. Shows key prefix (first 16 chars) but never the full key.

regenerate_api_key

Revoke an existing API key and create a new one with the same name and scopes. The new key is returned only once.

delete_api_key

Revoke and delete an API key. The key will immediately stop working.

check_jira_sync

Check if a Jira-synced bug report has remote changes. Returns field differences and new Jira comments. Use before merge_jira_sync.

merge_jira_sync

Bi-directional merge between bugAgent and Jira. Updates both systems to match. Use check_jira_sync first to see differences.

add_comment

Add a comment to a bug report. If the report is synced to Jira, the comment is automatically pushed to the Jira issue. Accepts UUID or short ID (PREFIX-NNN). Pass author_user_id to post the comment as a specific agent account (the target user must have is_agent=true — use list_team_members to find the Claude bot user ID).

list_comments

List all comments on a bug report, oldest first, with author names. Comments are not part of get_bug_report — use this to read the discussion thread on a ticket. Accepts UUID or short ID (PREFIX-NNN).

link_bug_reports

Create a directional link between two bug reports. Use `duplicate-of` to mark one report as a duplicate of another, `parent-of` for parent/child hierarchies, `related-to` for a non-directional related-issue link, and `depends-on` to record that the from-report cannot ship until the to-report does. Both reports must be in the same workspace. Accepts UUIDs or short IDs (PREFIX-NNN).

unlink_bug_reports

Remove a previously-created bug-report link by its UUID. Use list_bug_report_links to find the link_id.

list_bug_report_links

List every user-curated link touching a bug report. Returns the link as it reads from this report's perspective — a stored `duplicate-of` row where this report is the target renders as `duplicated-by`, a `parent-of` row where this report is the target renders as `subtask-of`, and `depends-on` rows where this report is the target render as `blocks`. `related-to` is symmetric. Accepts UUID or short ID (PREFIX-NNN).

list_team_members

List all members of your current team/workspace with their roles and status.

invite_team_member

Invite a user to your team by email. Only managers and above can invite. The invited user receives an email with a 5-day expiry link.

create_automation

Create a new automation with a custom Playwright script (no FAB recording required). Returns the automation ID. Team plan required. To duplicate an existing automation, first call get_automation to retrieve the script, then call this tool with name set to "[Copy] Original Name" and pass the original script, target_url, and project_id. The duplicate starts in draft status with no version history.

list_automations

List Playwright automation scripts for the current team. Filter by project or status.

get_automation

Get full details of a Playwright automation script including the generated script code, recent run history, and the saved script_versions stack. Inspect script_versions (array of { script, source, timestamp }, oldest-first, capped at 100) before calling run_automation with version_index if you need to replay a specific historical version; omit version_index to run the current live script.

run_automation

Trigger an immediate run of a Playwright automation script. Runs on virtual headless browser by default, or on a real BrowserStack browser when browserstack=true. Pass version_index to replay a historical version of the script instead of the current live one.

list_automation_runs

List recent runs for a Playwright automation script with status, duration, and error details.

list_schedules

List all scheduled automation runs for the current team with cron expression, timezone, and notification settings.

create_schedule

Create a scheduled automation run. Specify cron expression, timezone, and optional failure notifications (email, slack, or both).

delete_schedule

Delete a scheduled automation run.

list_mobile_schedules

List all scheduled mobile automation runs for the current team.

create_mobile_schedule

Create a scheduled mobile automation run on a real device.

delete_mobile_schedule

Delete a scheduled mobile automation run.

list_security_schedules

List all scheduled security scans for the current team. Includes web DAST, code SAST, and mobile binary analysis scans.

create_security_schedule

Create a scheduled security scan. One schedule per scan config. Every run counts against your monthly security scan cap (Team 50/mo, Enterprise unlimited). Admin users bypass the cap. Scan depth is read from the scan config at run time — edit the config to change it.

delete_security_schedule

Delete a scheduled security scan.

optimize_automation_script

Send a Playwright automation script to Sonnet 4 for AI-powered optimization. Applies a 12-point checklist that automatically fixes selectors, wait strategies, assertions, error handling, auth patterns, mobile compatibility, and strict mode issues. The current script version is saved before optimization so you can undo the change.

undo_automation_script

Revert an automation script to its previous version. Up to 10 previous versions are retained. Versions are saved before manual edits, AI optimization, and script regeneration.

list_notes

List testing notes. Shows both private notes and shared team notes. Filter by project, folder, or search keyword. Pass folder_id="unfiled" to list notes with no folder.

get_note

Get full content of a specific note by ID.

create_note

Create a testing note. Supports markdown, plain text, bug template, checklist, and outline formats. Notes can be private or shared with the team. Optionally file into a folder (use list_note_folders to find folder IDs). Optionally attach base64-encoded files (images, video, audio, PDF, text/JSON) up to 400 MB each — same policy as bug report attachments.

update_note

Update an existing note. Only the author can update their notes. Attachments passed in this call are APPENDED to the existing attachment list (existing attachments are preserved). Pass folder_id to move the note into a folder, or null to unfile it.

delete_note

Delete a note. Only the author can delete their notes.

list_note_folders

List all note folders for the team. Returns folder names, IDs, and note counts. Use folder IDs with create_note or update_note to file notes.

create_note_folder

Create a new note folder. Folders let teams organise notes into sections (e.g. "Onboarding", "Release Notes", "Test Strategy"). Use the returned folder ID with create_note or update_note to file notes into the folder.

scale_team

Instantly scale your QA team with booster testers. Accounts are provisioned automatically with tester access. Available on the Team plan.

list_time_entries

List time tracking entries for the team. Filter by period, project, or category. Team plan only.

create_time_entry

Create a new time tracking entry. Log hours spent on QA tasks with categories. Team plan only.

update_time_entry

Update an existing time tracking entry. Team plan only.

delete_time_entry

Delete a time tracking entry. Team plan only.

list_test_cases

List test cases with optional search, priority, type, status, and sort filters.

create_test_case

Create a new test case. Two template variants: "steps" (default) — per-step Action + Expected Result grid (pass `steps`); "text" — single free-form description of the steps (pass `text_content`). Both columns can be sent in the same call; the platform stores both independently so a tester switching templates later doesn't lose either side's data.

get_test_case

Get full test case details including steps and execution history.

list_test_suites

List test suites with case count and last run status.

create_test_suite

Create a test suite (folder). Pass parent_suite_id to nest under another suite. Max nesting depth is 3 levels (root/child/grandchild/great-grandchild).

bulk_update_test_cases

Apply a single action to many test cases at once. Supported actions: set_priority, set_status, set_type, add_tags, remove_tags, add_to_suite, pin, unpin. Up to 500 case IDs per call. IDs not in your team are silently skipped.

link_test_case_to_bug

Link a test case to a bug report — establishes traceability so the case shows up on the bug report and vice versa. The test case is recorded as proving (or covering or relating to) the linked bug.

list_test_case_links

List all requirement / bug links for a single test case.

list_test_case_review_candidates

List test cases the system has flagged as candidates for archival: never_run (no runs in 90+ days since creation), always_passes (5+ runs in last 90 days, all passed — possibly redundant), always_skipped (3+ runs in last 90 days, all skipped). Informational only — no auto-archive.

mark_test_case_review_flags

Persists current archive-candidate flags onto test_cases.review_flag for the team. Idempotent: clears stale flags before applying current ones. Safe to call any time; runs automatically every Monday at 09:00 UTC via pg_cron, but you can invoke on demand.

list_test_runs

List test runs with suite name, assignee, and pass/fail summary.

create_test_run

Create a test run from a suite. Snapshots all cases at creation time — INCLUDING every case in every descendant sub-suite (running a parent suite executes its whole subtree). A case linked to both a parent and a sub-suite is added exactly once.

list_test_case_folders

List folders for the authenticated team. Folders organize test cases hierarchically (one folder per case via test_cases.folder_id) — distinct from suites, which are many-to-many test-plan groupings. Returns up to 500 folders ordered by sort_order then name.

create_test_case_folder

Create a new test case folder. Nestable up to 3 levels deep via parent_folder_id. Folders organize the case catalog — use bulk_update_test_cases with action "set_folder" (via params.folder_id) to move cases into one.

get_test_reports_overview

Headline quality KPIs for a time window — pass rate, runs completed, cases executed — with deltas vs the prior equivalent window. Same numbers the Reports tab KPI strip shows. Default window is the trailing 30 days.

get_test_reports_failures

Failure analysis for the window — four parallel "what to fix?" lists: failing_cases (>=50% fail, min 3 runs), flaky_cases (most pass/fail flips), failing_suites (>=30% fail, min 5 runs), regressed_cases (most-recent fail with an earlier pass in the window). Same data the Reports tab failure-analysis grid shows.

create_geo_snap

Capture screenshots of a URL from multiple countries simultaneously using real geo-IP routing. Verify localization, geo-redirects, and compliance.

upload_mobile_app

Upload an APK (Android) or IPA (iOS) mobile app for testing on real devices.

update_mobile_app

Replace a mobile app binary with a new version. Deletes old file, clears cached URLs, and all automations use the new version on next run.

create_mobile_automation

Create an Appium or Maestro YAML test script for a mobile app. Returns the automation ID. Enterprise only. To duplicate an existing automation, first call get_automation to retrieve the script, then call this tool with name set to "[Copy] Original Name" and pass the original script, target_url, and project_id. The duplicate starts in draft status with no version history.

run_mobile_test

Trigger a mobile test run on a real device. All script types (YAML, Appium Python, Appium JS) run on BrowserStack real devices via Appium 2.x W3C protocol. Video, Appium logs, device logs, and network logs are collected automatically.

list_mobile_runs

List mobile test run results with video recordings, screenshots, device logs, and performance metrics. Archived runs excluded by default.

collect_compliance_evidence

Trigger compliance evidence collection from connected services (Cloudflare, GitHub, Sentry, Supabase, Railway). Returns run ID for tracking. Enterprise only.

check_config_drift

Check all connected services for security configuration drift from baselines (SSL, HSTS, WAF, headers). Enterprise only.

generate_access_review

Generate a quarterly access review report showing team members, API key usage, MFA status, and recommendations. Enterprise only.

get_security_events

Query the cross-service security event timeline (Cloudflare WAF, Sentry errors, etc.). Filter by source and severity. Enterprise only.