Bug Recorder
for LuumenAI
Record server-side errors in Bug Recorder from the terminal
When something breaks mid-investigation, log it where your team already looks. BUG_RECORDER_SEND_ERROR records one server-side application error in Bug Recorder and triggers whatever notifications the connected account has configured. Luumen connects with an API key, and the send is previewed for your approval by default.
The Bug Recorder toolbox
1 tools: 0 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- WriteSend ErrorRecord one server-side application error in Bug Recorder and trigger any notifications configured for the connected account. Approval by default
Questions
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 — send error — 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 Bug Recorder — 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.
Often connected alongside
All integrations
DynatraceProblems, root-cause detail, and metrics beside the session.
DatadogMonitors, dashboards, and logs pulled into the investigation.
GrafanaRead Grafana health, rings, and dashboard data, then push log records with approval
PrometheusAlerts, metrics, and traces from Prometheus in the session that fixes them.Put Bug Recorder to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.