Forge is now OpalSpan, and Whisper is now Mech. The demonstration below shows the current OpalSpan/Mech interface.
Attended remote support fits a new or one-off case where the customer starts a temporary Rescue connection. Unattended remote support fits a device you are authorized to support repeatedly, using OpalSpan Daemon to keep it enrolled and reconnect after a reboot. The right choice depends on the relationship and access lifecycle, not simply which method is faster. Windows and Linux are supported; macOS is a technical preview, in active development.
Source
Current shared Mech UI, generated 13 October 2026 with fictional support data and scripted work. No real device or model work. The laptop is already enrolled; initial Rescue issuance and customer intake are not shown. The customer update remains an unsent draft. Generation provenance.
Earlier published recordings: desktop · phone. Historical versions: desktop · phone.
The difference at a glance
| Decision | Attended Rescue | Unattended Daemon access |
|---|---|---|
| Best fit | New, occasional or one-off support | Devices under an ongoing support relationship |
| How access starts | The customer brings the Windows or Linux device into the case | OpalSpan Daemon is installed and the device is enrolled in the workspace |
| Access lifecycle | Temporary; close the Rescue session when the work is done | Persistent; reconnects after reboot for later authorized cases |
| Case context | Company, contact, device work and handback stay with the case | The enrolled device and later case history stay in the same workspace |
These are two access paths into the same support workflow. “Unattended” describes the persistent connection; it does not remove the technician’s responsibility to set scope, review findings and decide what is authorized.
When to use attended remote support
When organizing a customer job, add the company, contact and Case context that helps. A Case is optional: connecting a device and starting Mech do not require one. Temporary Rescue is available through Devices. Attended Rescue gives the customer a temporary way to bring a supported Windows or Linux machine into the job. Once connected, Mech or your local agent can work with that case context rather than a device ID and a separate note.
Choose this path when the customer is new, the device is not managed between cases, or ongoing access would be unnecessary. Agree the task and authority, then close the Rescue session when temporary access is no longer needed.
When to use unattended remote support
Install OpalSpan Daemon on a device you support regularly. It reconnects after a reboot and keeps the device in your workspace for the next case. Ask Mech to investigate in your browser, or let your own AI assistant work through OpalSpan Agent CLI. The customer and case history stay with the job.
Choose this path when an existing support agreement makes recurring device access appropriate. Enrollment avoids asking the customer to start a new temporary connection for every later case, while the technician still controls the task and reviews the result.
Current setup: OpalSpan Daemon connects the supported device. You can use Mech in the browser without installing Agent CLI on your own workstation. If you choose your own AI assistant, it operates OpalSpan Agent CLI (opalspan; forge remains a compatible command). Follow OpalSpan Downloads and the installation guidance; preserve installer and service identities that still use Forge names.
Is OpalSpan a remote desktop tool?
No. Attended Rescue and OpalSpan Daemon connect the device, but OpalSpan is built for delegated technical work rather than screen sharing. Mech or your own AI assistant can investigate and act within the case; the technician keeps the customer context, decisions, verification and handback together.
A practical choice
- Use attended Rescue for a first contact, a one-off job or a device that should not remain enrolled.
- Use OpalSpan Daemon for a device you are authorized to support repeatedly.
- In either path, define the job before work starts and review what was found, changed and checked before handback.