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.
4 tools: 3 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Bugbug run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
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.
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.
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.
Connect in minutes. Every action scoped, approved, and audited from day one.