Bugbug
for LuumenAI

Check BugBug suites and past runs, then start a test run with approval.

Connect BugBug and your browser test suites become something you can ask about from the terminal. List the tests in the account, see which suites exist, and read the details of a run that just failed. When you want a test executed again, Luumen names the test, waits for your approval, then starts the run and reports back. Authentication is by API key.

The Bugbug toolbox

4 tools: 3 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet test run detailsGet detailed information about test runs from BugBug.
  • ReadList suitesList all available test suites in the Bugbug platform.
  • ReadList testsRetrieves a list of all available tests in the BugBug account.
  • WriteRun testExecute a test in BugBug and return the test run details. Approval by default

One prompt, start to finish

What a governed Bugbug run looks like inside Luumen.

Questions

How does LuumenAI connect to Bugbug?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Bugbug on its own?

Read actions answer immediately. Anything that writes — run test — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Bugbug — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put Bugbug to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.