BugScribe for complete bug reports

Describe it once
BugScribe writes the report

From a one-line complaint to a complete, reproducible bug report, with replay, validity, duplicates, and a fix suggestion already taken care of.

app.lumen.work/settings/profile

Profile

Update how your name and email appear across Lumen.

MC

Display name

Maya Chenedited

Email

maya@lumen.work

Time zone

America/New_York

Pronouns

she/her

Loading workspace…

BugScribe Workspace

One surface.
Report on the left, agent on the right.

BugScribe is where a bug report becomes complete. The agent is always there, and every step is reviewable.

BugScribe· Session A84F2
Connected

Bug Report

Issue #BUG-A84F2

S2R (Steps to Reproduce)
1
2
3
Drag to reorder • Press Enter to add new step
Notes

Initially empty. Only modified by user

BugScribe Chat

Ready To File

AI-powered bug resolution and reporting

Bug report assessment
Valid
Confidence

93%

One edit to 'Observed' — adding the exact endpoint, status code, and repro count so the engineer doesn't have to ask.
Proposed Changes1 section

Tightens 'Observed' with endpoint, status, and repro count.

I found 1 similar open issue that may share the same cause:
#5211376.0% matchExisting

Profile save intermittently times out after identity-service deploy

76% match — same 504 on /api/profile, reported against last week's identity-service rollout.

View issue
1234
1

Structured bug report

Title, environment, steps, and behavior. The entire bug report, complete in a blink.

2

Agentic chat

Clarifying questions, triage, and investigation. The agent handles it all.

3

Validity & duplicates

Every report is checked for evidence quality and compared against your existing issues before it ships.

4

Non-destructive edits

The agent proposes changes to the report as diffs. You review, apply, or discard.

Investigation

Agents that
actually investigate.

Before the report leaves your site, specialised agents check report validity, cross-reference your existing issues, and suggest a fix.

Validity check

The validity agent inspects steps, environment, and the failure trace to confirm the report is evidence-backed and actionable before a human ever opens it.

Duplicate detection

Every report is instantly matched to your open issues. If it's a duplicate, you'll know immediatiely. No redundant tickets.

Bug report assessment
Valid
Confidence

93%

I found 1 similar open issue that may share the same cause:
#5211376.0% matchExisting

Profile save intermittently times out after identity-service deploy

76% match — same 504 on /api/profile, reported against last week's identity-service rollout.

View issue

Review

Every edit is a
proposal.

The agent never writes to the report silently. Each change arrives as a diff you can apply, tweak, or discard.

Proposals stack inline with the conversation. Apply them one at a time, batch-apply, or roll back later if the report changes direction.

Agent-authored, human-approved
Line-level diffs, not whole-block rewrites
Every applied edit is traceable back to its message
One small edit to "Observed" — adding the exact endpoint, status, and repro count so the engineer doesn't have to ask.
Proposed Changes1 section

Tightens 'Observed' with endpoint, status, and repro count.

Shipping

One click to
your tracker.

When the report is ready, BugScribe opens the issue in your existing tracker.

GitHub IssuesGitHub Issues
JiraJira

No new dashboard, no new process. If a ticket was going to live in GitHub or Jira, it still lives there. Zero vendor lock-in.

GitHub Issueslumen/admin-board
Submit to GitHub
Issue #2216 opened
github.com/lumen/admin-board/issues/2216

Context

See exactly what
the user saw.

Every report ships with a scrubbable session replay. Watch the bug happen instead of guessing.

Back to Report
Session Replay · #A84F2
1,248 events
app.lumen.work/settings/profile

Profile

Update how your name and email appear across Lumen.

MC

Display name

Maya Chenedited

Email

maya@lumen.work

Time zone

America/New_York

Pronouns

she/her

Couldn't save your profile

Request timed out. Please try again.

504 · POST /api/profile · 3.04s

504 · POST /api/profile · 3.04s
00:00 / 00:09
01spage loaded04sSave changes clicked07sbug triggered

What teams say

Reports your engineers
actually want to open.

One revealing question from our bug-reporting research: what do people struggle with most when writing a bug report?

Read the research
Describing clear steps to reproduce the issue
Explaining the expected vs. actual behavior
Capturing the issue at the right moment
Knowing what information is relevant
45.5%18.2%27.3%9.1%

Stop writing bug reports,
Start signing off on them

Drop a widget on your site. The next bug your users hit will arrive as a complete, validated report.