Suspending the host

💤 Suspend host puts the machine the relay runs on to sleep. You use it when you start long work in the evening and want the machine off once it is finished, without waiting up. The relay does not sleep the machine at once: it queues the request and waits until nothing is running any more.

It works only when the relay runs on Windows.

Using it #

1. Open the ⋯ menu in the chat header and choose 💤 Suspend host. The entry belongs to the relay, not to a conversation, so you need no open conversation.
2. The dialog Suspend host first reads Checking what is still running…, then shows one of two things:
   • Work is still active. It says Agents are still active. and lists what the relay waits for. The button reads 💤 Suspend when idle.
   • Nothing is running. It says that the host suspends 30 seconds after you confirm. The button reads 💤 Suspend host.
3. Confirm. A notice says Host suspend queued: the PC sleeps once all agents are done. or, when nothing was running, Host suspend queued: everything is idle, sleeping in 30 seconds. Cancel from the banner.

While the suspend is queued, the menu entry reads 💤 Suspend pending….

Where the entry is #

The entry is in the ⋯ menu and is on by default. The switch Show Suspend host action under Settings → General hides or shows it. The switch is saved per browser, so another device keeps its own value. It only controls the menu entry: the banner of a queued suspend shows on every device.

The entry is shown whatever the relay runs on. On a relay that does not run on Windows the dialog says Host suspend is only available when the relay runs on Windows. and has only a Close button. Switch the action off there.

How the wait works Added in 0.9.4 #

After you confirm, the relay checks every second. It sleeps the machine when nothing has been running for 2 minutes. If nothing was running when you confirmed and nothing has run since, the wait is 30 seconds instead. If work shows up during the 2 minutes, the clock starts again.

The relay waits for:

• Turns. A queued, running or parked turn in any conversation. A message waiting in a conversation's queue counts.
• Background tasks. A background task of an agent process that is still alive.
• GitHub Actions runs. An open run (not yet completed) in the GitHub repository of a conversation that was busy since you asked. The relay reads it with the gh command on the machine, in the repository's origin remote, and looks again about every 20 seconds. While it has not looked yet, the banner says Checking CI state and the suspend waits. If gh cannot read a repository, that repository blocks for 15 minutes, then is ignored.
• Failed checks. If the relay cannot work out what is active, it counts that as work and shows Activity check failed, so it never sleeps the machine under running agents.

A turn paused at the Claude usage limit counts as work when it resumes by itself, and does not when it waits for you to send the held message. See Usage limit pause.

What you see #

Every device that has the page open shows a banner, also a device where you hid the entry:

Cancelling #

Press Cancel in the banner. You can also open the ⋯ menu, choose 💤 Suspend pending… and press Cancel queued suspend. A notice says Queued host suspend cancelled.

A queued suspend is held in the relay's memory only. If the relay restarts, for example for an update, the request is dropped, and you must ask again.

The notification #

The push notification Host suspend fired or was dropped (title Host suspend) is on by default. It says All agents finished; the host is suspending now. when the machine goes to sleep, and Queued host suspend dropped: relay restarting. when a restart cancelled the request. See Notifications.

Troubleshooting #