Read Bugsnag projects, teams, and error data, then make changes with approval.
Connect Bugsnag and your team can ask about crash data in plain language. Check how events break down across a field, look up a saved search, review who is on a team, or check the status of a data deletion request. When something needs to change — a new team, an added collaborator, a bulk error update — Luumen shows the plan and waits for your approval before it runs. Auth is by API key.
60 tools: 36 read, 24 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Bugsnag 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.
This connection exposes write actions such as add collaborator to teams, add collaborators to team, bulk update errors, configure integration, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 Bugsnag — 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.