A screen wake lock keeps a visible display awake. It is not a system wake lock and does not control where an AI agent runs.
The Screen Wake Lock API has one job: prevent a visible device screen from dimming or locking. It can improve an AI workflow when a progress view, approval prompt, log, or preview must remain visible.
It does not keep a hidden tab active, guarantee network connectivity, prevent every operating system from suspending, or turn a local agent into a background cloud task.
Keep a browser-based task monitor, approval queue, or preview readable while you are nearby.
Prevent a screen from locking during an AI product demo or evaluation.
Use operating-system controls for agents, terminals, and servers that run on the device.
Only the AI service can define whether a remote task continues after you leave or disconnect.
Treat screen wake lock as a visible-session feature, not as job scheduling, background execution, or system power management.
It can keep the screen awake, but continuation depends on the agent architecture, browser visibility, network, and operating system.
Active screen wake locks are normally released when the document becomes hidden or inactive.
Only for a user-visible need, with clear active status, a stop control, and reacquisition handling after visibility changes.