Forge is now OpalSpan, and Whisper is now Mech. The demonstration below shows the current OpalSpan/Mech interface.
Customers bring symptoms, not command lists. In OpalSpan, the technician keeps the customer and case in view, chooses the device and tells Mech the outcome that matters. Mech carries the software work forward and leaves a record the team can use.
Source
Generated 13 October 2026 from the current shared Mech UI and a fictional Dell OptiPlex scenario. No real device or model work. Media provenance.
The request is enough to begin
In this example, printing has stopped. The technician can ask OpalSpan to get printing working on the selected machine and leave the case ready for handback. That is a useful outcome without scripting every command beforehand.
Mech inspects the print service, carries out the software correction and checks the queue. The technician can follow the actions and findings in the browser. The case keeps the work together, including the physical test print that still belongs on site.
Keep your attention where you want it
OpalSpan brings device work and the case update into one place. There is less copying between tools and less reconstructing the job afterward. Stay with another machine or customer, then return to the result and decide what needs your hands next.