Agent Awake

Version 1.4.0 is the standard stable release. Install or update normally; no pre-release opt-in is required. It promotes the same runtime as 1.3.0, without changing your settings or enabling protection automatically.

Click the ready coffee cup before a long run. Click the green cup when you are done.

Agent Awake requests local system and screen activity while you explicitly enable it. Use your normal Copilot, Claude, build, or other application; no replacement chat, model account, or @awake prompt is needed. Opening VS Code starts Off. The default active session has no expiry, but ends when you click again, turn Off, or close/reload its owning window.

Windows limitation: the screen stays on while enabled. Use AC power. Explicit Sleep, lid closure, lock/battery/company policies can override requests. Green means a native request was acknowledged, not immunity from forced sleep. Automatic Copilot activity detection is not implemented in this release.

The public name is Agent Awake. The original extension ID apkola29.agent-keep-awake and agentKeepAwake.* settings/commands are retained so existing installations receive an update instead of a second extension. This guide describes 1.4.0. An update installed on disk is not necessarily loaded in an existing window. Agent Awake: Show Status and Show Log report the version actually loaded in that window.

Optional experimental mouse jiggle

Agent Awake: Start Experimental Mouse Jiggle... remains an optional command in the stable release. It is Windows-only and remains unverified. The normal cup and native commands still use the original power-request route; there is no persistent mouse-jiggle setting and no automatic activation.

For supervised testing, start with Off, run that explicit command, and read its per-session warning. Only choosing Start mouse jiggle starts the helper. Canceling, turning Off while the warning is open, or leaving an existing session active will not silently enable input. It uses the configured Duration (Hours), including 0/until-off. Clicking its active cup, expiry, window close/reload or helper failure stops the owned session.

• One persistent Windows PowerShell helper waits 30 seconds between checks; no app/process is launched for each pulse, and no runtime package is added.
• It attempts a tiny paired relative mouse movement only after at least 30 seconds of input inactivity, with no mouse button or modifier held. It sends no clicks or keyboard events. Pointer acceleration/screen edges can affect the resulting movement; exact cursor restoration is not promised.
• It requires the unlocked physical-console desktop. Lock/session change or an inaccessible desktop stops it rather than attempting to unlock or resume. Unexpected exit never automatically restarts synthetic input.
• An unusable/future last-input timestamp stops with an explicit error rather than leaving a silently nonfunctional helper running.
• The command refuses activation inside an automated VS Code extension-test host. A normal or F5 development window still requires fresh human consent; automated tests must use the no-input guard checker instead.
• Initialization is bounded to 20 seconds because this route also verifies desktop/session access. A timeout releases the helper, so a late startup cannot begin input after reporting failure. Native startup keeps its existing 10-second bound.
• Synthetic input can affect pointer use and delay automatic locking. Use it only where device/organization policy permits. It does not change power plans, security settings or permissions, and never requests elevation.
• This route holds no additional native power request, reads no chat content, and does not detect Copilot/Claude work. It always shows Unverified, never confirmed green: a running helper is not proof that Windows will stay awake.

This optional feature is a compatibility experiment, not a measured CPU/memory improvement or a verified sleep fix. A stable release channel does not certify the experimental mouse mode. Automated checks do not send live synthetic input; the Windows startup check precloses stdin before initialization, so the movement loop cannot run.

The guard checker also executes the production pulse function and buffer allocation against a stub native class. It checks the paired mouse-only buffer, idle boundaries, held input, locked/changed desktop, canceled input, partial rejection and 32-bit tick wrap. These are control-flow and memory-layout checks, not evidence that a live Windows input event prevents sleep.

The native test:idle:windows checker is not mouse-jiggle acceptance: it requires a native system/display request and an unchanged last-input interval. Mouse mode intentionally resets the last-input timer and creates no native request. Its separate supervised acceptance must account for those generated events and rule out other wake sources. No live mouse-mode hardware pass has been recorded.

node .\test\os\verify-windows-guards.js

Use it in VS Code

Requirements: desktop VS Code 1.95 or newer. Manual power control needs no hooks, model account, API key, or subscription. Windows is the validated native-request target; macOS/Linux protection remains explicitly unverified.

以上为 README 的开头部分。其余内容请阅读原文。 查看完整 README ↗