A support job can take several questions. One colleague starts the investigation, another checks the result, and the conversation continues after a reconnect.
In OpalSpan, those changes do not each create another work session. A work session groups actual on-demand work on one device in one workspace within its activity window. Team members, Mech and your own external AI assistant share that window.
Follow the work, not the chat count
Imagine a technician asks Mech to investigate a Windows update problem. Mech collects fresh diagnostics, performs an authorized correction and checks the result. Twenty minutes after that work finishes, a colleague asks for a follow-up check on the same device.
Those operations share one work session, provided they remain on the same workspace billing date. Opening another conversation or reconnecting does not change that. This is an illustrative billing example, not a customer repair or a promised outcome.
A session starts or extends when the device accepts an authorized operation for execution. Fresh diagnostics, commands and device file operations count. A reservation or connection alone does not.
What changes the window?
A new session starts when actual work resumes after at least 60 minutes without device work, or when work occurs on a new calendar date in the workspace’s billing timezone.
A long-running operation is still work, even while it produces no output. Work continuing across midnight belongs to the new billing date too. An idle connection left open overnight creates no usage by itself.
Reading information already stored in OpalSpan, managing the workspace and chatting without device work do not consume work sessions. Mech’s AI usage is metered separately. An investigation can count even when its result is a useful blocker rather than a fix.
Follow a shared work session into the monthly report
A workspace Admin asks Mech what counts, then reads the fictional month summary in the current billing view. Mech AI usage is separate.
Source
Current shared Mech and billing components, generated 5 October 2026 with fictional usage. Offline illustration: no real account, AI call or device work. The example explains a stored work unit; it does not demonstrate a real repair or a customer’s bill. Actual device work after at least 60 idle minutes, or on a new billing date, starts a new unit. Silent running operations remain work.
Keep the next bill deliberate
New DKK Shop, Business and Fleet orders include 300, 1,500 and 5,000 monthly work sessions respectively. Additional paid-session spending starts with a zero monetary budget; an authorized customer must approve more.
For Fleet, sessions 5,001–20,000 cost DKK 1.50 each. Only sessions above 20,000 cost DKK 1.00 each. Earlier sessions are not repriced when you cross a band. All amounts exclude VAT; Stripe shows the exact applicable total. AI top-ups remain explicit purchases, and existing accepted orders keep their own terms.
Start with Mech in the browser. If you prefer your own AI assistant, it can use OpalSpan Agent CLI with the same user permissions and work-session rule; you do not need to operate a terminal yourself.
Windows and Linux are supported; macOS is a technical preview, in active development.