Skip to main content
A cloud agent’s computer includes a shared desktop and Chromium browser. The agent and authorized people use the same browser session.

Open the desktop

Select Desktop in the agent view, or click its sidebar desktop preview. A preview is available while the desktop is running; its absence does not mean the agent has no saved files. Opening Desktop does not wake a sleeping agent. Start permitted work or enable the agent when appropriate. Older computers may show a setup or update notice before the desktop becomes available.

Watch or take control

Watching requires read access to the agent. Taking control requires the same authority as messaging it; Worker desktops do not offer human control. Use Take control to interact with the desktop. While you hold control, the agent’s browser commands are paused. This is a browser handoff, not a pause of every agent task or background process. Choose Release control, or leave the Desktop view, to hand the browser back to the agent. Type directly into the desktop; there is currently no clipboard bridge.

End a desktop session

End desktop session closes the desktop’s browser windows and disconnects viewers. It requires control authority and does not stop the agent itself. Use Start new session to open another desktop session while the agent is available. A later agent browser action can also start it again. Ending the desktop does not wake an offline computer. Saved browser sign-ins are retained in the computer’s browser profile across normal sleep and desktop-session restarts. Ending a desktop session is not the same as signing out of websites.

Access, work, and costs

The desktop belongs to the agent’s shared computer, so treat visible browser content and signed-in accounts as part of that agent environment. Agent access is rechecked while connected. An open desktop does not by itself prevent automatic sleep. The computer’s harness and work state determine sleep eligibility; Grok Build currently has no automatic sleep. See The agent computer for file retention, wake-up, and runtime costs, and Agent settings to disable an agent when you want it kept stopped.