Operator chat
One conversation that owns the outcome, not just the reply.
Product
One operator. The whole workstream.
You give the operator an outcome. It plans, delegates, acts through approved systems, and comes back with results and evidence — inside boundaries you set.
The Cell lifecycle is real state.
A Cell is normally paused. Nothing in the product describes a Cell as live unless the provider confirmed it in that check.
StateWhat it meansReads as
Not provisionedNo computer has been attached to this workspace yet.unprovisioned
ProvisioningThe Cell is being created. Files and browser profile are not ready yet.provisioning
PausedFiles and browser state are kept. Compute resumes when work starts.paused
ResumingCompute is starting back up from the saved state.resuming
RunningCompute is live and billed for as long as the Cell stays awake.running
PausingWork finished. The Cell is saving state and going back to sleep.pausing
FailedThe provider reported a fault. The Cell is not usable until it is repaired.failed
DeprovisionedThe Cell was removed. Nothing is running and nothing is stored.deprovisioned
Every surface in the workspace.
Company memory
Durable facts you can read, edit, export, and delete.
Instructions
The operating rules injected before every run.
Specialists
Narrow agents the operator delegates to, each with its own scopes.
Skills
Versioned manifests you inspect before installing.
Connectors
Provider-confirmed authorizations with visible scopes.
Cell
An isolated computer with persistent files and browser state.
Automations
Recurring work with a schedule the runtime has confirmed.
Runs
Durable status, steps, artifacts, evidence, and cancellation.
Approvals
A person decides before anything consequential happens.
Credits
Reserve, settle, release, and an itemized receipt per run.
Data
Export everything, or request deletion.
Built around one physical idea.
A machine on a desk that holds your work between visits. It sleeps when you are not asking for anything, and everything it did is written down.
