Skip to content
Weavz
Menu

Give your AI a computer. Stay in control.

Let your agent use a cloud desktop with a browser, files and a terminal. Watch its screen, take over when needed, then choose when to return control.

Read the setup guide
Cloud computerExample session
BrowserFilesTerminal
Research workspace

Research, ready to review.

Open a source. Check the details.
Save a note for the next step.

research-notes.md
Agent has control

An authorized person can watch, then take over when needed.

Try the handoff. This example does not start a remote computer.

See the work. Step in when it matters.

Use app integrations for supported API actions. Add a visible computer when the task needs a desktop, a browser and a terminal together.

Give the agent a visible place to work.

Add Computer Control to an MCP Workspace. Your agent starts a bounded session and uses screenshot, click, type, file and terminal tools as the task requires.

Watch and control are separate.

An agent can provide a short-lived watch link. Human control needs separate authorization. Taking over interrupts agent commands before your input is accepted.

Return control when you are ready.

A disconnected controller leaves the session paused. An authorized person takes control again and explicitly returns it to the agent.

For your AI

Add a computer to the MCP Workspace connected to your AI. Watch the work and use your authorized dashboard access when you need to take over.

Connect your AI client

For your product

Embed the live viewer in your product. Your authenticated backend issues short-lived watch or control access for the particular person and session.

Explore the API

A few useful details.

Understand the boundaries before you build a workflow around them.

What computer does the agent use?

Computer Control provides a cloud Linux desktop with a browser, files and terminal. It does not grant access to your personal computer. Your AI client or application provides the agent; Weavz provides the computer tools.

Can I stream the screen and take over?

Yes. Short-lived watch access lets an authorized person view the screen. Taking over needs a separately authorized control link. A trusted backend can issue access and embed the viewer for an authenticated user. An ordinary MCP token cannot mint human control access.

What persists after a session?

Files saved under /workspace can be restored for the same user and configured alias after a successful checkpoint. Browser sign-ins, open applications, running programs and unsaved work are discarded. Checkpoints have file-count and size limits described in the documentation.

How is computer time charged?

A session reserves available prepaid Sandbox time from the plan. Confirmed unused time is returned after shutdown. Session duration and concurrency limits apply. Unlimited connected accounts and MCP Workspaces do not mean unlimited computer time; see the current pricing and plan limits.

Start with one useful task.

Connect your AI, or explore the setup for your product.