Reporting Bugs

Use the in-app Report a Bug button in the lower-right corner of the admin app to send a bug report without leaving the page you are on.

How to Open It

You can open the bug report panel in two ways:

• Click the floating bug button in the bottom-right corner.
• Use the keyboard shortcut:
• Ctrl+Shift+B on Windows
• Cmd+Shift+B on Mac

This opens a right-side panel where you can describe the issue and send the report.

What Gets Captured Automatically

When you submit a report, CleanEstimate Pro automatically captures:

• The current page URL
• Page title
• Recent page history
• Browser and operating system
• Viewport and screen size
• Last detected action
• Recent console errors
• Recent failed network requests
• Session and app version details
• A screenshot of the current app window

The automatic screenshot captures the page state you were looking at when you pressed Send Report.

Note: The screenshot is taken automatically on submit, so you do not need to attach one manually for most reports. If automatic capture fails, the form now tells you right away so you can still send the report or attach one yourself.

Replacing the Automatic Screenshot

The Screenshot section still lets you attach your own image.

Use that if you want to:

• Replace the automatic capture with a cropped or annotated image
• Upload a screenshot from another device
• Share a screenshot taken before the issue changed state

Images over 2MB are compressed before upload. Final upload size is capped at 5MB.

Filling Out the Report

The most useful reports include:

• What went wrong?
• What were you trying to do?
• What did you expect to happen?
• Severity
• Category

If you are short on time, the description is the only required field. The diagnostic context and screenshot do a lot of the rest automatically.

Owners and managers are no longer capped at only five reports per hour. The app still applies a server-side abuse limit, but it is set high enough for real bug sweeps.

Offline Behavior

If you are offline when you submit a report:

• The report is queued locally
• The app keeps the captured details
• The report submits automatically when the browser comes back online

If your session expires during submission, the draft is restored after you sign back in.

Who Can Review Reports

Submitted reports are reviewed from Admin --> Bug Reports. That review page is limited to owner accounts, and the owner inbox now stays tied to the owner's accessible org scope instead of disappearing or shrinking down to only the currently switched child workspace.

That view is where your team can:

• Open the full report
• Track the report by its bug number, such as BUG-0042
• Review the screenshot
• Read diagnostics and reproduction notes
• Update the report status
• Track whether the issue is new, acknowledged, in progress, resolved, or won't fix
• Review the automated intake verdict before escalating it
• Open the linked GitHub issue when bug-duty sync is enabled

GitHub Bug Duty

When GitHub bug sync is configured, CleanEstimate Pro can push strong bug reports directly into your repository as bug issues.

The app does not blindly sync every report. It first scores each submission for signal quality using the report details, reproduction notes, and captured diagnostics.

• Accepted reports sync automatically to GitHub and receive the openclaw:auto label for runner pickup
• Needs review reports stay in Admin --> Bug Reports until an owner decides to push them
• Rejected reports are treated as likely training or low-signal submissions and stay out of the repo by default

If GitHub is unavailable, or if an owner wants to override the automatic gate, the bug report detail page includes a manual Sync to GitHub action.

If sync fails, the bug report detail page now shows the sync error instead of looking like a silent no-op.

To enable GitHub bug-duty sync, configure the production app with:

• GITHUB_BUG_REPORTS_REPO
• GITHUB_BUG_REPORTS_TOKEN

For instant OpenClaw pickup without cron polling, install the self-hosted runner on the always-on machine and keep these repo files in place:

• .github/workflows/openclaw-bug-dispatch.yml
• dispatch-bug.sh

The runner listens for issues with all of these labels:

• bug
• triage:accepted
• openclaw:auto

The workflow adds openclaw:started before dispatching so the same issue cannot be picked up twice.

Best Practices

• Submit the report as soon as the bug happens so the automatic screenshot reflects the right state.
• Add one sentence describing what you clicked just before the problem started.
• If pricing, totals, or customer data look wrong, mark the severity accurately so the team can triage it faster.
• If the issue blocks work entirely, use High or Critical.