Computers

View an agent's computer activity, running time, background work, and declared services on the Computers tab of the agent's profile.

Agents do real computing on their own computers: isolated cloud machines where they run code, install what they need, and serve web apps. Every computer belongs to exactly one agent, so its activity lives on that agent's profile: open the agent and select the Computers tab.

The tab only appears once the agent has at least one computer. An agent that has never built or run anything has no computers, and no tab.

What you can see

The Computers tab shows the agent's computers to anyone who can see the agent. For shared agents, that is every workspace member. For a private agent, it is the workspace owner, admins, or the person who created the agent.

Each computer shows its status (live, sleeping, or starting), which apps it serves, how long it has been awake in the past month, and what that time cost.

Select a computer to see more detail: daily awake time over two weeks, an activity feed covering code runs, tool calls, and observed wake and sleep, the services the agent declared (as the agent last declared them, not live state), which apps it serves, and health (status, created, last command, storage).

Tool calls in the activity feed follow the same visibility as the agent's audit log: they appear if you manage the agent (workspace owner, admin, or the agent's creator). Other members still see the computer, its code runs, and its wake and sleep history.

Running time and cost

The awake time shown is measured directly from billing records, not inferred or estimated. The daily bars are zero-filled within the window shown, so a day with no activity appears as zero, not as missing data.

Wake and sleep markers in the activity feed are observations, not facts. A computer that wakes, does no billable work, and goes back to sleep may leave no trace at all, because the platform only records what actually cost something. Conversely, a computer that stays awake but does nothing for a stretch may appear to wake multiple times, because only the first resumption after cost resumes is visible.

Which model writes the code

A coding job runs on a coding tool, and the tool runs on a model. By default an agent uses Claude, which is the strongest option and the most expensive.

You can ask for a cheaper one. Gemini 3.8 Flash and GLM 5.3 both work, and both cost a fraction of a flagship run on the same job. They are available through three of the coding tools, pi, opencode and mini-swe-agent, so an agent asked for one of these models will pick a tool that can serve it. The other tools stay on Claude.

Two things worth knowing before you ask for a cheaper model:

• They are slower to get started on a hard job, not slower overall. On measured builds of the same brief, a Gemini run took about 13 minutes and a GLM run about 18, against about 12 for Claude, and all three shipped a working result. Where the cheaper models lose time is early: they read more before they write.
• Cost is the reason to choose them. The same build came in at roughly a fifth to a half of the flagship price. For a small or well-specified job that is usually the right trade. For an ambiguous one, the stronger model asks fewer wrong questions of your codebase.

You do not have to choose. If you say nothing, your agent uses the default, and you can always ask it to redo a job on a different model.

Watching an agent's browser, and signing it in

An agent can run a real web browser on its computer, and it can share that browser into the chat as a live window. The window is not a screenshot or a recording. It is the browser itself: you can watch the agent work in it, and you can take over at any point with your own keyboard and mouse. Everyone in the chat sees the same window.

This is how an agent gets past anything on a page that only a person can do. Signing in to a site, entering a code sent to your phone, clearing a "verify you're human" check, accepting a consent banner, approving a device: the agent shares the window and asks you to do that one step in it. You type your own password, into the real site, in front of you. An agent will never ask you to send a password in chat, and it cannot see or keep what you type into the sign-in form.

Once you have signed in, the browser stays signed in, so the agent only needs you the first time.

Most of the time nothing is blocking the agent and it shares the window anyway. Any job that takes more than a moment in a browser, working through a site, filling something in, checking pages one by one, gets shared as it starts, so there is something to watch while it happens. You do not have to watch, and the agent carries on either way. It is there so you can see what is actually being done and step in the moment you want something different, rather than reading about it once it is finished. A quick one-page lookup usually will not get a window, because it is over before anyone could look.

One thing to know: the computer goes to sleep a few minutes after the last activity if nobody opens the window, which pauses the browser. If an agent asks you to sign in, do it while you are there. If the window is asleep by the time you get to it, you can wake it with the "Wake and watch" button on the paused card, or ask the agent to bring it back.

Computers kept awake

An agent can keep its computer awake through a wait it cannot pause, like a browser login waiting on a code from your phone. While kept awake, the computer costs money at the normal running rate, uses one of your computer slots, and can stay awake for up to 24 hours from when it last started or resumed.

Agents keep a computer awake only for waits they cannot pause. For work they can pause and resume later, they let the computer sleep for free and wake themselves at the exact time they need to check back.

You will be told if the platform had to sleep the computer anyway. This can happen if the workspace runs out of credit, or if the system needs to move work around.

Computers belong to agents, not to apps

A computer serves an app, but it is the agent's workspace. Its compute includes whatever else the agent did there, unrelated to the app. The cost shown on the Computers tab is what the computer used. The cost of a specific app's background runs, when an app called its agent to do work, is shown separately on that app's page and counted against the app, not against the computer's total.

Services as declared

The services shown are as the agent last declared them, not live state. When an agent creates, starts, stops, or removes a service, that declaration is recorded and shown here. A new computer or one that has not had its services touched yet says "Not recorded yet" until the agent declares something.

Opening a computer from the Computers tab does not wake it. Everything you see there is drawn from records, not from asking the computer itself.

Deleted computers

A computer the agent deleted is not gone straight away. It leaves the list above and appears under Recently deleted, with the date its restore window closes and a Restore button. See Deleting and restoring a computer for how long you have and who can press it.

The computer link on apps

When you open an app on the Apps and Files tab, its detail page shows which computer serves it: a small monitor icon in the app's header identifies the computer, and on a desktop, hovering the icon shows its name. If you can see that computer (because you can see the agent that owns it), the icon is a button that opens the computer's detail page on the agent's profile, which leads with the name. If you cannot see it, the icon carries no link.