Getting started
Start with a job on a customer's computer or server: investigate a fault, configure a service, deploy software or perform maintenance. OpalSpan enables you to use AI agents to carry out the device work your customer pays you to deliver.
Create or select your workspace. A Case or personal setup meeting is optional. Invitation and workspace rights come from current membership/policy, not Auth0 claims or an old selected-device list. Workspace creation honors the requested return destination; first-device setup is the default. The current Work overview shows case/attention context, not a claim that the landing page is always Mech or a live relationship map.
Choose how to work
Use Mech in the browser, or let your own assistant operate OpalSpan Agent CLI. The assistant uses opalspan; you authorize ordinary sign-in and supervise, not manually operate a command workflow.
opalspan login
opalspan whoami
opalspan doctor
opalspan capabilities
Use a separate profile where identity/workspace isolation is needed. Browser Mech and local-agent conversations are distinct. No token extraction, copied credential cache or filesystem shortcut. Windows/Linux are supported; Mac is technical preview.
Connect and authorize a device
For work on a computer or server, enroll it for persistent Daemon access or use attended Portable Rescue. The recipient approves target-local actions; a shared link/invitation is not consent. Keep codes and generated packages private and follow their exact page instructions. No support account, tray app or inbound LAN listener is required. Access explains scope and stop/expiry.
Do one useful task
Tell the agent what your customer needs, which device to work on and what work is allowed. Include relevant symptoms, constraints and any decisions you want to make yourself. Choose an explicit bounded diagnostic when useful; it is not mandatory before every task, and a page read does not collect evidence. Review the actual result, save Case notes/drafts when they help, and review customer text before manual handback. No guaranteed repair or automatic email is implied. Automations have separate schedule/target/credit and local-consent boundaries.
Work on your own devices and internal IT environments uses the same routes. Agents can also organize company/contact records, link customer and device records, and manage team/workspace settings within your permissions. These supporting actions need no live device connection or Case.
Failure and private reports
Preserve drafts, images and original receipt/request identity on failed or uncertain submission. Read original outcome before retrying a mutation. Use the single Report a bug entry; its existing Thank you remains unchanged. Reports go privately to OpalSpan issues with original S3 downloads. Anyone holding the fixed 90-day bearer link can download without login until expiry; keep it private. Production defaults/old versions are not current release proof: see releases.
Work sessions and handback
Device-accepted operations share one workspace/target work unit until at least 60 minutes of inactivity or another billing date with actual work. Silent running work continues; idle connections/keepalives/stored reads do not count. Billing is not execution consent or repair success. Review the result. If a customer handback is useful, review the exact draft before manual export; see access and Cases.