Skip to content
Weavz
Menu

Computer Control

Give an agent a cloud desktop, watch its screen, and take over through a separately authorized human control link.

Computer Control gives an agent a cloud Linux desktop with a browser, files and a terminal. Use it when a task needs desktop interaction alongside app APIs. Weavz provides the computer tools; your AI client or application provides the agent.

An agent can start a session, inspect the screen, click, type and run commands. A person can watch, take over, then explicitly return control. Watching never grants control, and the agent cannot issue itself a human control capability.

Choose the right tool

NeedUse
Send a message or update an app record through a supported APIThe app's integration action
Navigate websites and inspect page structureAgent Browser
Use a desktop application, browser and terminal togetherComputer Control
Run a computation without a visible desktopSandbox

Computer Control is optional. Add the computer-control integration under an alias such as computer. Every session is tied to one organization, workspace, configured alias and end user. Files from a different user or alias do not become available simply because they share a workspace.

Control belongs to one actor

The normal flow is Start → Agent control → Human takeover → Return control → Agent control → End.

  • An agent's live-view action returns a short-lived watch link.
  • A signed-in, authorized person or your trusted backend obtains a separate control link.
  • Selecting Take over interrupts running agent commands before human input is accepted.
  • Closing the controller, losing the connection or allowing its lease to expire pauses the computer. The agent does not automatically resume.
  • A person takes control again and chooses Return control to let the agent continue.

Completed actions are not undone by takeover. Inspect what is on screen before continuing, especially before sending a message, submitting a form or changing an account.

What persists

StateAfter a session ends
Files saved under /workspaceRestored for the same user and configured alias, subject to a successful checkpoint
Browser sign-ins and cookiesDiscarded
Open applications, running programs and unsaved workDiscarded
Files outside /workspaceDiscarded

A checkpoint supports up to 256 regular files, 8 MiB total and 1 MiB per file. Save durable results under /workspace. Status reports checkpoint failures; a failed save retains the last good checkpoint. Ending the session still stops compute even when persistence fails.

Time and capacity

A session reserves time from your plan's available Sandbox allowance before it starts. The default is up to 10 minutes, adjusted to the available prepaid time, with a maximum of 30 minutes per session and two concurrent sessions per organization. Confirmed unused time is returned after shutdown. A session also ends after an idle period; watching alone does not keep it alive.

Unlimited connected accounts and workspaces do not mean unlimited computer time. Finite plan capacities are prepaid limits, without automatic overage charges. Review plan limits before long tasks.

Access and supported tasks

The initial computer supports public HTTP and HTTPS access. Private network addresses and non-HTTP protocols are unavailable. Use app integrations for account access where possible. Browser sign-in may still require the person to complete authentication or a challenge in the live view.