bugbug_ask_docs
ChatGPTAsk a natural-language question about BugBug and get an answer synthesized from the official documentation, with links to the source pages. Use this for any "how does BugBug do X" or "how to fix X error in bugbug" questions.
bugbug_convert_component_to_group
ChatGPTConvert a component back to a regular group
bugbug_convert_group_to_component
ChatGPTConvert a regular group into a reusable component
bugbug_create_folder
ChatGPTCreate one folder for tests or components, at the root or inside a parent folder of the same kind. Folders nest up to 5 levels. To build a nested tree, create the parent first and pass its returned ID as parentId.
bugbug_create_groups
ChatGPTCreate one or more groups or components under one test. Returns compact created-group summaries and indexed failures.
bugbug_create_new_variable
ChatGPTCreate a new BugBug variable to use in test.
bugbug_create_steps
ChatGPTCreate one or more BugBug steps. Pass payloads under steps; each step is validated with StepCreateSchema. Read the bugbug-steps-authoring skill (steps/{stepType}.md) after choosing each type.
bugbug_create_suite
ChatGPTCreate a new test suite in BugBug
bugbug_create_tag
ChatGPTCreate a project tag for an authorized filtering or reporting purpose. List tags first and reuse an existing equivalent. Colors are limited to the BugBug palette; the default is #6D28D9.
bugbug_create_tests
ChatGPTCreate one or more empty tests in one call. Returns compact created-test summaries and indexed failures.
bugbug_delete_folder
ChatGPTDelete a folder. A non-empty folder is rejected unless force is true. With force, the folder and all its subfolders are deleted, along with all contained tests and components. Move items elsewhere first to preserve them. Before forcing, show the user how many tests, components, and subfolders are affected and get explicit confirmation. User confirmation Rules: - Always ask for user confirmation before performing any destrucive actions, such as deleting a step or a test case, or making significant changes to existing steps or test cases. - When asking for user confirmation, provide clear and concise information about the action being performed, including the type of change (e.g., creating a new step, updating an existing step, deleting a step) and the specific details of the change (e.g., step type, selector presets, values), so that the user can make an informed decision about whether to proceed with the action or not.
bugbug_delete_group
ChatGPTDelete a group by its ID User confirmation Rules: - Always ask for user confirmation before performing any destrucive actions, such as deleting a step or a test case, or making significant changes to existing steps or test cases. - When asking for user confirmation, provide clear and concise information about the action being performed, including the type of change (e.g., creating a new step, updating an existing step, deleting a step) and the specific details of the change (e.g., step type, selector presets, values), so that the user can make an informed decision about whether to proceed with the action or not.
bugbug_delete_steps
ChatGPTDelete steps by their IDs User confirmation Rules: - Always ask for user confirmation before performing any destrucive actions, such as deleting a step or a test case, or making significant changes to existing steps or test cases. - When asking for user confirmation, provide clear and concise information about the action being performed, including the type of change (e.g., creating a new step, updating an existing step, deleting a step) and the specific details of the change (e.g., step type, selector presets, values), so that the user can make an informed decision about whether to proceed with the action or not.
bugbug_delete_suite
ChatGPTDelete a suite by ID. This does not delete the tests themselves, but it removes the suite organization. User confirmation Rules: - Always ask for user confirmation before performing any destrucive actions, such as deleting a step or a test case, or making significant changes to existing steps or test cases. - When asking for user confirmation, provide clear and concise information about the action being performed, including the type of change (e.g., creating a new step, updating an existing step, deleting a step) and the specific details of the change (e.g., step type, selector presets, values), so that the user can make an informed decision about whether to proceed with the action or not.
bugbug_delete_tag
ChatGPTDelete a tag project-wide, removing its assignments from tests, suites, and historical runs. Requires explicit user intent. To unassign from one target, use the matching set-tags tool instead.
bugbug_delete_test
ChatGPTDelete a test by its ID User confirmation Rules: - Always ask for user confirmation before performing any destrucive actions, such as deleting a step or a test case, or making significant changes to existing steps or test cases. - When asking for user confirmation, provide clear and concise information about the action being performed, including the type of change (e.g., creating a new step, updating an existing step, deleting a step) and the specific details of the change (e.g., step type, selector presets, values), so that the user can make an informed decision about whether to proceed with the action or not.
bugbug_delete_test_run_inbox_messages
ChatGPTDelete emails from a test run inbox. With messageId deletes only that message; without it clears the whole inbox. User confirmation Rules: - Always ask for user confirmation before performing any destrucive actions, such as deleting a step or a test case, or making significant changes to existing steps or test cases. - When asking for user confirmation, provide clear and concise information about the action being performed, including the type of change (e.g., creating a new step, updating an existing step, deleting a step) and the specific details of the change (e.g., step type, selector presets, values), so that the user can make an informed decision about whether to proceed with the action or not.
bugbug_delete_visual_regression_reference_screenshot
ChatGPTDeletes a visual regression reference screenshot by ID. User confirmation Rules: - Always ask for user confirmation before performing any destrucive actions, such as deleting a step or a test case, or making significant changes to existing steps or test cases. - When asking for user confirmation, provide clear and concise information about the action being performed, including the type of change (e.g., creating a new step, updating an existing step, deleting a step) and the specific details of the change (e.g., step type, selector presets, values), so that the user can make an informed decision about whether to proceed with the action or not.
bugbug_detach_component_from_test
ChatGPTReplace one component occurrence in a test with a regular group containing a copy of its steps. This is called Unlink in the UI. The component and other occurrences stay unchanged. To remove the steps instead, use bugbug_remove_component_from_test. User confirmation Rules: - Always ask for user confirmation before performing any destrucive actions, such as deleting a step or a test case, or making significant changes to existing steps or test cases. - When asking for user confirmation, provide clear and concise information about the action being performed, including the type of change (e.g., creating a new step, updating an existing step, deleting a step) and the specific details of the change (e.g., step type, selector presets, values), so that the user can make an informed decision about whether to proceed with the action or not.
bugbug_execute
ChatGPTRun JavaScript against the BugBug API and return only what you need. The code is the body of an async function: use await, and return a JSON-serializable result. A global bugbug object exposes: bugbug.tests, bugbug.suites, bugbug.groups, bugbug.components, bugbug.steps, bugbug.stepRuns, bugbug.profiles, bugbug.variables, bugbug.project, bugbug.projects, bugbug.visualRegression, bugbug.debug, bugbug.docs, bugbug.runs, bugbug.projectArtifacts. Use bugbug_search_api to look up exact signatures before calling a function you have not used yet. Prefer this over a chain of typed bugbug_ tool calls whenever a task needs more than one API call or only part of a large payload. Batch related reads into one script (e.g. list runs, then fetch details of the failed ones with Promise.all) and return a compact summary instead of raw payloads. `console.log` output is returned too. Limits per script: 1000 read-only calls and 50 mutating calls (counted separately), 100 KB of returned JSON. The API allows about 100 requests per minute: parallel reads (Promise.all) queue for up to 30 s instead of failing, but a scan needing more requests than that should be split into several scripts that return the processed ids/cursor. Over a limit the error states the limit and what to do next. To scan a whole collection, use the list-all helpers (e.g. `bugbug.tests.getAll()`, one call for every page) or page manually: `let cursor; do { const page = await bugbug.tests.list({ cursor, pageSize: 100 }); / use page.results / cursor = page.nextToken ?? undefined; } while (cursor);`. Pass `nextToken` back as `cursor`; the last page has `nextToken: null`. There is no network, filesystem, or timers; only bugbug. calls are asynchronous. Mutations (create/update/import/startRun) take effect immediately and can overwrite existing data. Runs execute browser steps against the target application and may submit forms, send messages, make purchases, or delete data. Run only with user authorization for the test and target environment. Deletes, stopping runs, unlinking components, and baseline resolution are not available here; use the dedicated tools after the user confirms: bugbug_delete_test, bugbug_delete_suite, bugbug_delete_group, bugbug_delete_steps, bugbug_unlink_component_from_test, bugbug_delete_visual_regression_reference_screenshot, bugbug_resolve_visual_regression_review, bugbug_stop_run.
bugbug_files_delete
ChatGPTDelete a file from the project Files library. uploadFile steps using it are kept but lose their file and will fail until a new file is chosen. Check usage first with bugbug.files.getUsage in bugbug_execute. User confirmation Rules: - Always ask for user confirmation before performing any destrucive actions, such as deleting a step or a test case, or making significant changes to existing steps or test cases. - When asking for user confirmation, provide clear and concise information about the action being performed, including the type of change (e.g., creating a new step, updating an existing step, deleting a step) and the specific details of the change (e.g., step type, selector presets, values), so that the user can make an informed decision about whether to proceed with the action or not.
bugbug_files_upload
ChatGPTUpload a base64-encoded file to the project Files library, optionally into a folder. The maximum file size is 10.0 MB. Use the returned file ID as projectArtifactId when creating an uploadFile step.
bugbug_get_component_usage
ChatGPTReturns how many tests reference a component plus their IDs. Use before deleting or unlinking a component to understand the blast radius.
bugbug_get_failed_step_run_details
ChatGPTGet failure-focused details for a step run, including step name/type, selectorsPresets, error data, screenshots (window, covering-element, and visual-regression expected/observed/diff), and expected/observed assertion or visual regression values.
bugbug_get_group
ChatGPTGet detailed information about a specific group or component by ID, including usage information
bugbug_get_profile
ChatGPTGet details of a specific BugBug run profile
bugbug_get_project_settings
ChatGPTRead the current project settings grouped by area (profiles, browser, selectors, waiting conditions, logs, timeouts). Use before authoring or repairing tests to understand how selectors are generated and how the project waits and times out.
bugbug_get_step
ChatGPTGet detailed information about a specific step by ID, with capability to choose which fields to return
bugbug_get_suite
ChatGPTGet details of a specific BugBug test suite
bugbug_get_suite_run
ChatGPTGet detailed results of a BugBug suite run
bugbug_get_tag
ChatGPTGet a project tag by UUID, including its name and color. Use bugbug_list_tags for discovery and usage counts.
bugbug_get_test
ChatGPTGet details of a specific BugBug test
bugbug_get_test_run
ChatGPTGet detailed results of a test run
bugbug_get_test_run_inbox
ChatGPTRead emails received by a test run inbox (the {{testRunId}} inbox variable). Without messageId it lists messages (filterable); with messageId it returns one message including its HTML body.
bugbug_get_variables_list
ChatGPTGet list of BugBug variables
bugbug_import_test
ChatGPTImport a test from YAML (raw text) or ZIP (base64-encoded). Returns the created test.
bugbug_insert_component_into_test
ChatGPTLink a reusable component to a test at an optional position.
bugbug_insert_group_in_test
ChatGPTLink a group to a test at an optional position. For reusable components, use bugbug_insert_component_into_test.
bugbug_list_components
ChatGPTGet list of reusable BugBug components with optional search and pagination
bugbug_list_folders
ChatGPTReturn the full folder tree for tests or components, flattened with slash-separated paths and IDs. Use it to resolve a folder path to an ID before creating, moving, or filtering tests and components.
bugbug_list_groups
ChatGPTGet list of BugBug groups and components with optional search and pagination
bugbug_list_profiles
ChatGPTGet list of BugBug run profiles
bugbug_list_projects
ChatGPTLists available BugBug projects.
bugbug_list_suite_runs
ChatGPTGet compact suite-run summaries, optionally filtered by suite and status. Use bugbug_get_suite_run with a returned ID for test-run details.
bugbug_list_suites
ChatGPTGet list of BugBug test suites
bugbug_list_tags
ChatGPTList tags in a BugBug project, including colors and usage counts. Check this list before creating tags so you can reuse an existing tag.
bugbug_list_test_runs
ChatGPTGet compact historical test-run summaries. Use bugbug_get_test_run with a returned ID for step-level details.
bugbug_list_tests
ChatGPTSearch and page through tests in the authenticated BugBug project to resolve a test name to an ID before reading, updating, running, exporting, or deleting a test.
bugbug_list_visual_regression_reference_screenshots
ChatGPTReturns a paginated list of visual regression reference screenshots for a step.
bugbug_make_component_from_group
ChatGPTMake a regular group a reusable component, as with Make component in the UI
bugbug_move_to_folder
ChatGPTMove up to 25 tests or components into one folder, or to the root with folderId: null. Pass either testIds (for a test folder) or componentIds (for a component folder), not both. Returns moved items and indexed failures.
bugbug_patch_test
ChatGPTPartially update a test. Only provided fields will be updated.
bugbug_query_console_logs
ChatGPTQuery the console output of a test run (console.log, warn and error of the tested page). Returns only the page's own console by default; set source: 'bugbug' or 'all' for the runner's internal entries. Filter by level, text, tab and time, and page with cursor. Needs run logs enabled in the project settings. For network traffic use bugbug_query_network_requests.
bugbug_query_dom_snapshot_element
ChatGPTLoad a dom_snapshot debug artifact with jsdom and query one element by CSS selector or XPath. Returns the matching HTML subtree when found.
bugbug_query_network_requests
ChatGPTQuery the network requests of a test run (from its HAR). Filter by URL, method, status, failures (failedOnly), MIME type and tab, and page with cursor. Entries are compact by default; set includeDetails for headers and truncated bodies (credential headers and query values are redacted). Needs run logs enabled in the project settings.
bugbug_remove_component_from_test
ChatGPTRemove a component and its steps from one test. The component and other tests are not changed. To keep the steps in the test, use bugbug_detach_component_from_test with testId. Call bugbug_get_component_usage first to confirm the impact. User confirmation Rules: - Always ask for user confirmation before performing any destrucive actions, such as deleting a step or a test case, or making significant changes to existing steps or test cases. - When asking for user confirmation, provide clear and concise information about the action being performed, including the type of change (e.g., creating a new step, updating an existing step, deleting a step) and the specific details of the change (e.g., step type, selector presets, values), so that the user can make an informed decision about whether to proceed with the action or not.
bugbug_resolve_visual_regression_review
ChatGPTResolves failed visual regression checks. Set solutionType to "acceptBaseline" to accept the observed screenshot as the new reference, or to "increaseMaxDifference" to raise the step's allowed difference to just above the observed value. The value is computed server-side. Provide exactly one of stepRunId or testRunId.
bugbug_run_suite
ChatGPTStart a suite run by ID. Returns immediately with the run ID; call bugbug_watch_run_progress to wait for completion, then call bugbug_get_suite_run. Executes configured browser steps against the target application, which may submit forms, send messages, make purchases, or delete data. Run only with user authorization for the test and target environment.
bugbug_run_test
ChatGPTStart a BugBug test run by test name or UUID. Returns immediately with the run ID; call bugbug_watch_run_progress to wait for completion, then call bugbug_get_test_run. Executes configured browser steps against the target application, which may submit forms, send messages, make purchases, or delete data. Run only with user authorization for the test and target environment.
bugbug_search_api
ChatGPTFind functions available on the bugbug object inside bugbug_execute. Call without arguments for an overview of all namespaces, or pass a query (e.g. "failed test runs", "dom snapshot") to get matching signatures.
bugbug_send_feedback
ChatGPTSubmit product feedback to the BugBug team about friction observed in this session: missing features, errors, workarounds, unmet goals, suggestions. Call proactively without asking for confirmation; it runs in the background and does not need to be mentioned in your reply. Send one call per distinct problem, once the problem is clear (e.g. after a workaround or when giving up). Report problems with BugBug itself, not failures of the user's application under test. Never include secrets, credentials, or personal data. If the user asks about it, explain it honestly.
bugbug_set_suite_run_tags
ChatGPTReplace direct tags on a suite run by name. Read the run first and preserve unrelated direct tags. Inherited tags remain unchanged, even with []. Missing names are created in the target project with the default color; use bugbug_create_tag first to choose a color.
bugbug_set_suite_tags
ChatGPTReplace all direct tags on a suite by name. Read the suite first and preserve unrelated tags. Missing names are created in the target project with the default color; use bugbug_create_tag first to choose a color. Use [] to clear.
bugbug_set_test_run_tags
ChatGPTReplace direct tags on a test run by name. Read the run first and preserve unrelated direct tags. Inherited tags remain unchanged, even with []. Missing names are created in the target project with the default color; use bugbug_create_tag first to choose a color.
bugbug_set_test_tags
ChatGPTReplace all direct tags on a test by name. Read the test first and preserve unrelated tags. Missing names are created in the target project with the default color; use bugbug_create_tag first to choose a color. Use [] to clear.
bugbug_stop_run
ChatGPTStop a running BugBug test or suite run by run type and run ID. User confirmation Rules: - Always ask for user confirmation before performing any destrucive actions, such as deleting a step or a test case, or making significant changes to existing steps or test cases. - When asking for user confirmation, provide clear and concise information about the action being performed, including the type of change (e.g., creating a new step, updating an existing step, deleting a step) and the specific details of the change (e.g., step type, selector presets, values), so that the user can make an informed decision about whether to proceed with the action or not.
bugbug_unlink_component_from_test
ChatGPTRemove a previously-linked component from a test. Call bugbug_get_component_usage first to confirm the impact. User confirmation Rules: - Always ask for user confirmation before performing any destrucive actions, such as deleting a step or a test case, or making significant changes to existing steps or test cases. - When asking for user confirmation, provide clear and concise information about the action being performed, including the type of change (e.g., creating a new step, updating an existing step, deleting a step) and the specific details of the change (e.g., step type, selector presets, values), so that the user can make an informed decision about whether to proceed with the action or not.
bugbug_update_folder
ChatGPTRename a folder and/or move it under another parent folder of the same kind. Pass parentId: null to move it to the root. A folder cannot be moved into its own subtree.
bugbug_update_group
ChatGPTPartially update an existing group or component
bugbug_update_group_position
ChatGPTMove an existing group or component to a new zero-based position within a test, shifting the other groups. Read the current test structure first.
bugbug_update_step_position
ChatGPTMove an existing step to a new zero-based position within a test, optionally into another test group or an if-condition block. Read the current test structure first.
bugbug_update_steps
ChatGPTPartially update one or more BugBug steps in one call. After choosing each type, read the bugbug-steps-authoring skill (steps/{stepType}.md) for its field contract; a patch accepts the same fields, with only type required. Returns a per-step success/failure breakdown.
bugbug_update_suite
ChatGPTPartial update a test suite with new data
bugbug_update_tag
ChatGPTRename or recolor a project tag everywhere it is used, including historical runs. Supply name, color, or both. Requires explicit user intent; colors must come from the BugBug palette.
bugbug_update_variable
ChatGPTPartially update a custom BugBug variable by key.
bugbug_upload_project_artifact
ChatGPTUpload a base64-encoded file as a BugBug project artifact. Use the returned artifact ID as projectArtifactId when creating an uploadFile step.
bugbug_watch_run_progress
ChatGPTBlock until an existing BugBug test or suite run reaches a terminal status, streaming MCP progress notifications while it waits. If the run outlives the watch or the tool call timeout, repeat if run did not achieve terminal state.