Skip to main content
Agents can only reach a rig while Windows is awake and the host agent is connected. Keep rig awake prevents system sleep so the rig remains available for new sessions.

​
What it does

When enabled, the host asks Windows to keep the system awake while the Glasswarp agent is connected:
  • Windows does not enter system sleep from idleness.
  • The host remains connected and ready for an agent or remote session.
  • The physical monitor may still dim or turn off normally while no session is active. Keeping the system reachable does not keep the screen lit.
  • During an active API or streaming session, the host also asks Windows to keep the display awake.
This is a software availability control. It does not power on a machine that is shut down or already asleep.

​
Turn it on

Go to Console → the rig → Settings → Keep rig awake. The rig must be online when you change the toggle because the preference is sent over its live host connection. The host persists the preference, so it survives agent and machine restarts.

​
When it is off

The host keeps Windows ready while it is actively in use, then releases its system sleep block after the idle window (3 hours by default). Windows follows the machine’s normal power settings after that and may sleep. Once Windows sleeps, Glasswarp cannot start a session until someone or something outside Glasswarp wakes the machine.
The host environment variable PROJECTX_KEEP_ALIVE_IDLE_TIMEOUT controls the idle window in seconds. Set PROJECTX_KEEP_ALIVE=0 to disable the keep-alive mechanism entirely.
  1. Leave the Windows machine powered on.
  2. Keep the Glasswarp host agent running and signed in.
  3. Enable Keep rig awake.
  4. Let Windows turn off the monitor normally when idle.
This keeps the rig reachable without wasting power on an illuminated display. See also Rigs and sessions.