Read BugHerd projects and tasks, then file the fix as an approved step
BugHerd collects issues reported straight from a live site, which means the backlog fills up faster than anyone reads it. Connect it and Luumen can list projects, walk the tasks on a board, and check who has access — all without leaving the terminal. When something needs to be filed, commented on, or assigned, that change is previewed and approved first.
26 tools: 13 read, 13 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Bugherd 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 guest to project, add member to project, create attachment, create column, 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 Bugherd — 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.