Forge is now OpalSpan, and Whisper is now Mech. The demonstration below shows the current OpalSpan/Mech interface.
A customer sends a screenshot and a setup log. Give both to Mech and ask it to examine the evidence. You can start the investigation from what the customer actually saw, without retyping an error or picking through the log first.
Source
Current shared Mech UI, generated 13 October 2026 with fictional supplied logs/error report and scripted analysis. No real image interpretation, device inspection or model call. Files and the next-check handback are local example data. Generation provenance.
Earlier published recordings: desktop · phone. Historical versions: desktop · phone.
From two files to a useful next check
In this fictional example, the screenshot shows 0x800f081f and the log reports that the update service stopped during setup. The illustrated response brings those clues together and suggests checking the service and component state on the PC before choosing a repair.
That gives the technician a specific thread to investigate. The attachments provide the starting evidence; checks on the connected device establish what is happening now.
Use the originals throughout the case
Mech can read screenshots, PDFs and text or log files. You can revisit the originals while their attachments remain available. Conversation uploads are temporary; keep important evidence in the technician’s authorized case record as well. Conversation file identities are not a guarantee that the original bytes remain accessible.
Try it with a support file you already have permission to use. Add it to a Mech conversation and ask what it tells you about the next step.