Local Lens
How to make a silent visual bug report in Local Lens
Prepare a visible starting state, record the action that triggers the bug, and leave the unexpected result on screen before stopping. This Local Lens version records silent video only. Preview the take, download it explicitly, and confirm the file is saved before discarding. Pauses count toward its five-minute wall-time limit; there is no editing or recording history.
Plan a report the viewer can understand silently
Use this Local Lens version for a short visual reproduction: the starting state, the action, and the unexpected result. For example, show a form with a filled delivery address, select Save, and leave the validation message visible. The video should show enough context for someone to repeat the action without hearing you explain it.
No microphone or shared audio is requested or recorded. Put the expected result and any necessary explanation in the written bug report that accompanies the downloaded file. Local Lens has no caption, annotation or editing tools, so arrange the demonstration before capture rather than relying on an explanation added inside the app afterward.
Choose a source that shows the whole reproduction
Open the app over HTTPS or localhost in a desktop browser with screen-capture and MediaRecorder support. Select Start recording, then choose the screen, window or tab in the browser prompt. Choose a source that includes the controls and result you intend to show. Hide personal notifications before recording and avoid including unrelated information.
Check Your source, the live preview, before doing the important action. Wait for the recording state and advancing clock. If sharing is cancelled or denied, the app offers Start recording again; check browser or operating-system permissions before retrying. Local Lens cannot bypass the permission prompt or silently choose your source.
Show one failure within the wall-time budget
Show the initial values, perform the triggering action once, and allow time to read the result. Avoid moving immediately to another screen: a visible error message is often the useful endpoint. Use Pause and Resume for an interruption, but remember that pausing does not grant extra time.
This version stops after five minutes of wall time, including pauses, or at 100 MiB of encoded data. For example, one minute recording, two minutes paused and one more minute recording consume about four minutes of the wall-time allowance. Plan any lengthy setup before Start recording. The size threshold is a guardrail: a final chunk may exceed it, and total memory use can be higher.
Review the evidence before attaching it
Select Stop when the failure is clear. Ending sharing through the browser also asks Local Lens to finish the take. Wait for Your take to show the finished video, then play it. Check that the starting values, triggering action and final message are visible and understandable without sound. Protected surfaces may appear blank, so do not assume the live demonstration produced useful footage.
Select Download video explicitly; stopping does not save a file automatically. The app chooses a browser-supported WebM or MP4 recording format, with no conversion control. Check the file information and confirm the download has completed before attaching it to your report. Download placement follows your browser settings.
Keep or replace the take deliberately
Start recording remains disabled while the finished take exists. If the report needs another attempt, first save any footage worth keeping, then select Discard take. That clears the in-tab preview and lets you start again. There is no history of earlier attempts and no tool to combine them.
Recording data stays in tab memory without uploads or persistent storage. Closing or reloading loses an unsaved take; the browser leave warning is not a backup and may be suppressed. Discard removes the in-tab video, but it does not delete files already downloaded to your device. Keep the saved file until you have finished using it in your report.
AI-assisted ForgeHub editorial. App capabilities were checked against its implementation; this guide is not an independent review.
Frequently asked questions
Why is there no sound in my bug recording?
This Local Lens version deliberately records silent video only. It requests no microphone or shared audio. If the bug depends on sound, this recording cannot demonstrate that part; describe it separately in your written report.
Does pausing freeze the five-minute timer?
No. The limit measures wall time from recording start, including pauses. Pause and Resume let you interrupt the captured action, but the five-minute deadline continues.
Can I trim out a mistake before downloading?
No editing or trimming is implemented. Review the finished take, save it if useful, and discard it before recording a replacement. There is only one in-tab take at a time.
Does a recording failure leave a recoverable video?
A normal Stop or sharing-ended event prepares a preview when video data exists. A recorder error reports that the take could not be recovered, and an empty capture asks you to start again. Do not assume a file exists unless a usable finished preview and download are available.