AI Workforce OneHQDocs

When a Cloud Computer sleeps

An AI Team Cloud Computer that nobody is using goes to sleep and wakes exactly as it was. What keeps it awake, and what happens to a question Claude asked that nobody answered.

An AI Team Cloud Computer that nobody is using, and that has no work running, goes to sleep after about 15 minutes. Sleep keeps its memory. When it wakes, every session is exactly where it was, including what is on its screen.

What keeps it awake

  • Someone is at the team: in HQ in the browser, in VS Code or with hq.
  • Claude is working: writing an answer, running a tool, or a process it started is still using the processor.
  • A command in a terminal session is using the processor, such as a long build that prints nothing. A terminal waiting at its prompt does not keep it awake.
  • Any other program on the Cloud Computer is using a noticeable share of the processor, such as a job left running in the background.
  • Remote control (/remote-control) is on in a session.
  • A scheduled prompt is due soon.
  • An app preview is in use.
  • An AI Employee is waiting on a "Needs you" request (for up to 30 minutes).

A question nobody answered

Claude sometimes stops to ask you something: a question with choices, a plan to approve, a permission prompt, or a menu such as /model. The session then waits for you.

Today, a Cloud Computer with a question open on screen stays awake until the question is answered. Letting it sleep behind a question that nobody is answering is coming, and is off for now. When it is on, it works like this.

Work can go on behind the question: subagents, background commands, test runners and containers keep running. So the Cloud Computer stays awake while any of this is true:

  • any command Claude started is still running, attached to the session or detached from it (with nohup, &, or in tmux or screen), even one that looks stuck or uses no processor;
  • a command is running in a terminal of the Cloud Computer;
  • a Docker container is running, or a Docker build or pull is in progress;
  • a program left running in the background is listening on a port;
  • something on the Cloud Computer is using more than a little of the processor (2 % of one core, measured over the last two minutes).

It can go to sleep once the question has sat completely still, at the earliest 15 minutes after the last time the session's screen changed, a new command started, or any of the above was true. The other rules on this page still apply, so it can stay awake longer.

If anyone typed into the session, or a prompt was delivered to it (a schedule or an API message), after Claude's status line was last on screen, the Cloud Computer stays awake until the question is answered. The same holds if remote control was on in that session the last time its status line was on screen, so you can still answer from your phone.

Sleeping never answers the question. When you come back, the Cloud Computer wakes and the question is still on screen, waiting for you.