For the repair bench

More bench work moving. Less case work left behind.

Put Mech on a supported software job while you handle physical repairs, customer conversations and the machines that need your hands. Come back to a checked result and a usable case record.

Windows and Linux supported. macOS technical preview.

Create accountSee plans and pricing

A practical first step

Start with the work you need.

Made for: Repair shops with several active Windows or Linux jobs and one technician keeping the whole picture.
Start with: One bench PC that needs a software investigation, correction or clear handback.

See OpalSpan at work

Watch the case move forward.

EXPLORE MECH · OPALSPANInteractive fictional example

OpalSpanFictional local example

Task context · Bench PC 03Ready

Focus: Bench PC 03Case: Update service failure

You control this conversationSaved permissions and scope apply

You

Six PCs are on the bench. Start with PC 03: diagnose the failed updates, repair within scope, verify it and finish the case record.

Try the example controls. Fictional device, conversation and Case; no real AI or device work is started.

INSIDE MECH · OPALSPANTask, checks and handback

Restore one bench PCâ€™s update service, check the scan and save the useful handback.

Source

Generated from the current shared Mech interface with fictional data and scripted responses. This is a simulation, not real device work or measured AI timing. Repair-shop generation, 13 October 2026. Other bench devices are left untouched.

01 / THE WORKFLOW

Give each job its own place

Keep the customer, machine and reported problem attached to a case, even when several machines are on the bench.

02 / THE WORKFLOW

Let Mech take a software thread

It can investigate, carry out supported changes and check the result while you work on another machine.

03 / THE WORKFLOW

Finish the handback

OpalSpan records the findings and checks. You decide the physical next step and review what the customer should hear.

04 / THE WORKFLOW

Keep your shop system

OpalSpan does not replace repair tickets, inventory, invoicing or point of sale. It adds authorized device-software work and case evidence; attended Rescue or the enrolled Daemon provides access instead of generic screen sharing.

Another path for the bench

Keep investigating when Windows will not boot.

Boot a locally prepared repair USB and OpalSpan can help gather drive evidence, keep the case current and show what needs your hands next.

EXPLORE MECH · OPALSPANInteractive fictional example

OpalSpanFictional local example

Task context · Repair Live USBReady

Focus: Repair Live USBCase: Machine no longer boots

You control this conversationSaved permissions and scope apply

You

The machine is already booted from our prepared repair Live USB. Investigate without writing to its disk and document the safest next step.

Mech

Reasoning

I'll use the **already locally booted** Rescue environment for read-only storage evidence. I won't run repair scans or write to the disk.

execute on rescue Result received

Arguments

{
  "operation": "Read-only storage health and filesystem inventory"
}

Result

{
  "nvme_health": "critical warning",
  "media_errors": 184,
  "filesystem": "not mounted",
  "writes_attempted": false
}

Repeated media errors make a failing drive likely, but not yet physically confirmed. Write-heavy repair could reduce recovery options.

add case note Result received

Arguments

{
  "case_id": "demo-case"
}

Result

{
  "saved": true,
  "status": "Blocked",
  "blocker": "No verified backup or approved recovery destination"
}

Repair paused to protect the data

No writes were attempted. The case records the critical storage evidence and the blocker.

Next: confirm backup status, agree a recovery destination and physically assess or replace the drive before repair continues.

Try the example controls. Fictional device, conversation and Case; no real AI or device work is started.

INSIDE MECH · OPALSPANTask, checks and handback

Keep the storage evidence and next recovery decision without writing to the affected drive.

Source

Generated from the current shared Mech interface with fictional data and scripted responses. This is a simulation, not real device work or measured AI timing. Recovery generation, 13 October 2026. An enrolled bench PC is shown, not a Live USB boot, recovered files or a physical repair.

See the repair workflow →

A practical guide to the workflow

Follow a computer repair from failed updates to handback

Bring your next support case.

Create your account and workspace, choose a published plan and connect a Windows or Linux device. Start with the task you need done. You can set up and use OpalSpan yourself; help is optional.

Create accountOptional help with setup Plans and pricing