Forge is now OpalSpan, and Whisper is now Mech. The demonstration below shows the current OpalSpan/Mech interface.
A Windows PC on the bench has stopped completing updates. The technician has other machines and customers to look after. In this illustrative OpalSpan run, Mech takes the software thread: find the cause, make the correction, check the result and leave the case ready for handback.
Source
Current shared Mech UI, generated 13 October 2026 with fictional bench data and scripted work. No real device or model work. The task restores the update service and checks a scan; it does not install updates, restart the PC or work on the other bench devices. Generation provenance.
Earlier published recordings: desktop · phone. Historical versions: desktop · phone.
What happens in OpalSpan
- The job has a home. The technician opens Mech in the browser with the bench PC and its update-service case in view. The customer context and machine stay attached to the work.
- Mech carries the software work. In the demo it checks the component store and reboot state, finds a stopped update service, restores it and runs a fresh update scan.
- The result is ready to use. The scan completes without errors. OpalSpan records the finding, correction and check in the case instead of leaving the technician to reconstruct them later.
A six-step checklist for delegated software repair
Use the same sequence whether Mech works in the browser or your own AI assistant uses OpalSpan Agent CLI:
- Capture the request. Put the reported symptom, customer context and the correct device in one case.
- Set authority. Decide what the agent may inspect and which changes require technician approval before work starts.
- Investigate. Gather the device facts that can explain the symptom instead of jumping from the request straight to a generic fix.
- Correct the cause. Carry out only the authorized software change and keep the action attached to the case.
- Verify the result. Repeat the relevant check—in this demonstration, a fresh Windows Update scan—and record whether it completed cleanly.
- Prepare the handback. Summarize what was found, changed and checked so the technician can review the result and explain it to the customer.
This is a workflow checklist, not a promise that every repair can be automated. Hardware work, ambiguous findings and decisions outside the agreed authority stay with the technician.
That is the part worth trying in a real shop. You choose a case to hand to OpalSpan, stay with the work that needs your attention, and come back to a technical result and case record you can actually use. Sometimes that means more time for a tricky repair; sometimes it means finishing the customer conversation without another half-written note waiting for you.
OpalSpan works with supported Windows and Linux devices; macOS is a technical preview, in active development. The technician uses the browser; Mech does the device work. Bring a case your team already has, and see how the workflow feels in your shop.