Give your agent a computer you can watch and take over.
Let an agent work with a browser, desktop applications, files and a terminal on a cloud Linux computer. Watch its work, take control when needed and explicitly return control before it continues.
Computer Control gives a configured workspace alias and end user a time-bounded computer session. Use it for work that needs a desktop or terminal. Keep structured app actions for operations the integration already supports, and use Agent Browser when the workflow only needs a browser session.
Use a desktop when the job needs one.
A computer is another tool in the workflow. Give it a clear task, a bounded session and a result the person can inspect.
Work across browser and desktop apps
Observe the desktop, interact with the browser and use supported mouse and keyboard actions. Check the current screenshot and target before making a change, especially after navigation or a sign-in interruption.
Prepare and inspect files
Read, write and list files in /workspace, and use the terminal for supported commands. Keep useful outputs there so they can be checkpointed. Review a generated report before it becomes a customer-facing document.
Bring a person into the session
Show a short-lived watch link when someone needs to see the work. Request human takeover to pause the agent. Human control is granted separately, and the person must explicitly return control before agent operations continue.
Make the handoff part of the setup.
- Step 1
Configure the computer and user
Add Computer Control to the workspace and identify the end user. The computer and saved files belong to that user and configured alias. Inspect structured app actions first when a desktop is unnecessary.
- Step 2
Reserve time for a specific task
Start a session with the time the task needs, up to 30 minutes. Computer time reserves available sandbox seconds. Unused reserved time is returned after the computer’s stop is confirmed.
- Step 3
Watch, take over and return control
Use the live view to inspect the session. Grant human control through a signed-in user or trusted backend when needed. Return control explicitly after the person finishes, then end the session when the task is complete.
A watch link is not a control grant.
Keep the operator, session identity and next action clear at every handoff.
Keep human control explicit
The agent receives watch access and can request a pause. It cannot grant itself human control or override the person’s takeover. Your trusted backend or an authorized signed-in user issues the separate control access.
Stop at unexpected state
A changed page, missing target or login prompt should interrupt the workflow. Refresh the observation and bring in the person instead of repeating a click against an uncertain screen.
Keep files and browser state distinct
Successful checkpoints preserve supported files under /workspace for this user and alias. Browser sign-ins and running applications end with the session. Check the reported save status before assuming the latest changes are available next time.
Apps for this workflow
Open an app to check its current actions and setup. Provider permissions and available operations vary by integration.
Build the first version.
Use the setup path that matches who will operate the workflow. Connect your accounts and verify a small task before enabling broader access.
Set up the integration deliberately
Follow the integration guide for the session identity, supported actions and human access. A general workspace template does not enable computer control by itself.
Inspect Computer Control actionsQuestions before you start
What survives when the computer session ends?
Successfully checkpointed files under /workspace can be restored for the same workspace, configured alias and end user. Browser sign-ins and running applications do not persist. Checkpoint limits are 8 MB total, 256 files and 1 MB per file. A failed save retains the last successful checkpoint.
Can the agent give itself human control?
No. The agent can return a watch link and request human takeover, which pauses agent work. A trusted application or authorized signed-in user grants control separately. The person must explicitly return control before the agent can continue.
Is a computer an always-on background service?
No. Sessions are time-bounded, up to 30 minutes, and use reserved sandbox time. Idle sessions stop. End the session when the task finishes; unused reserved time is returned after stop confirmation. Check your plan’s available sandbox allowance.