Can Lyro create or edit a BugBug test?

No. The toolkit exposes four actions - Run Test, Get Test Run Details, List Suites and List Tests - so Lyro can start a test and report on it but cannot record, author or modify one. Test authoring stays in BugBug.

Can Lyro control which browser or viewport a run uses?

Yes. Run Test takes optional browser, device, viewport and variable overrides, and returns the run ID, its status and a URL to the detailed results in the BugBug web application, so Lyro can hand back a link a developer can open directly.

Can Lyro run a whole suite in one go?

Not as a single call. List Suites tells Lyro which suites exist so it can say what a suite contains, but Run Test triggers one test at a time - there is no run-suite action in this toolkit.

How is this different from a scheduled BugBug run or a Zapier trigger?

A schedule fires on a clock and a Zapier step fires on one fixed event. Lyro decides inside the conversation whether a test is worth running and which one, then reads Get Test Run Details - which supports filtering by start time and sorting - to report execution history in the same exchange.

Bugbug MCP integration

Triggers a named browser test, reports its status, timing and errors, and lists what the account actually covers.

Connect Bugbug See all integrations

4actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Get test run details
Lyro retrieves detailed information about test runs from BugBug. Agents see exact pass/fail results and timing for investigation.
List tests
Lyro retrieves a list of all available tests. Agents find which tests exist without leaving the chat.
Run test
Lyro executes a test in BugBug and returns results immediately. Customers verify fixes without manual test platform access.

See all 4 actions

How businesses use Bugbug + Lyro

Each card is one request a support team gets, and the Bugbug actions Lyro runs to close it.

Trigger a test run and report the outcome
Lyro starts the requested test with the browser, device and viewport it should use, then reads the run back and returns the status, timing and any error detail with a link to the full results.
Run TestGet Test Run Details
Answer what the test account already covers
Lyro lists the tests in the account with their active and recording status, and the suites they are grouped into, so a question about coverage is answered without anyone opening BugBug.
List TestsList Suites

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Bugbug actions it has and picks the ones a request needs.

01
Connect Bugbug
Authorize the Bugbug account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Bugbug actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Bugbug · Lyro

Everything else about Bugbug

Setup, permissions, and the limits of what Lyro can do inside Bugbug.

No. The toolkit exposes four actions - Run Test, Get Test Run Details, List Suites and List Tests - so Lyro can start a test and report on it but cannot record, author or modify one. Test authoring stays in BugBug.