Send Feedback
Submit a bug report or feedback. Optionally bundles the project and recent logs.
The Send Feedback dialog is how you report bugs and send feedback. It bundles your current project (optionally), the app version and build, and recent logs so I can see the same state you did.
This is the single most useful thing you can do when something goes wrong.
When it opens
- Menu: Help → Report a Bug or Send Diagnostics.
- From Connection Diagnostics panel → Send to Beam Bench (pre-fills connectivity context).
Fields
| Field | Type | Notes |
|---|---|---|
| Title | text, max 500 chars | Short summary. Required. |
| Description / Note | textarea, max 50,000 chars | What happened, what you expected, what you tried. Required for bug / crash reports. |
| Reply-to Email | text, max 255 chars | Optional. Lets me follow up. |
| Include Project File | checkbox | Bundle the current .lzrproj project with the report. Disabled if the project is over the size limit. |
| Preview toggle | toggle | Reveals the exact JSON payload that will be submitted, so you can verify nothing private leaks. |
Buttons
- Cancel: dismiss without sending.
- Save Report to File: write the report locally (useful if you want to attach it to a Facebook post or share manually instead of submitting).
- Submit: send to the Beam Bench feedback endpoint.
For connectivity-kind reports, the submit button reads Send to Beam Bench instead.
Notes
- The dialog enforces character limits with live validation.
- Project size is probed asynchronously. If your project is too large to attach, the checkbox disables and a note explains.
- After submission, a success screen shows the report ID. Keep this for follow-up.
- After save-to-file, the success screen shows the saved path.
- The dialog title changes based on report kind: Bug Report vs Connectivity Report.
Related
- About dialog: app version (same info bundled)
- Connection Diagnostics panel: file connectivity-specific reports
- Community & support