Awake for Codex

Keep your Mac awake while Codex works in VS Code.

Awake follows Codex turns, VS Code tasks, terminal commands and timers. A small flame in the status bar pulses amber, orange and red while work is active. Hover it to see which workspaces are keeping your Mac awake.

Public pre-release · Apple Silicon Macs · Local VS Code 1.140 or newer

Connect Codex

1. Install Awake and the Codex extension, then open a trusted workspace folder.
2. Awake automatically installs four activity hooks. In Codex, approve the Awake: Codex activity hooks.
3. Reload VS Code and start a new Codex turn in that workspace.

No separate Node.js installation or setup command is needed for a fresh install. Initial approval in Codex is required. Hooks installed confirms configuration, not approval; use Awake: Codex Setup Help if the flame remains idle.

Routine Awake upgrades preserve the hook definitions. Moving VS Code or changing the signal directory can require setup and approval again.

See it in VS Code

Real VS Code captures from an isolated demo workspace using simulated events.

Small controls, shared visibility

• Hover the flame for status, active workspace names and quick controls.
• Click the flame for all controls, including timers and diagnostics.
• Pause or resume one window without interrupting another window's protection.
• Use system mode to prevent idle system sleep, or display mode to also keep the display awake.
• Disable animation in settings if preferred. Reduce Motion and high-contrast themes keep the active icon steady.

An idle window may show a colored flame when another workspace is working. The hover distinguishes this window's activity from other active workspaces. Tasks and terminal commands also count, including long-running watch commands.

Privacy

Awake runs locally, with no telemetry or runtime network requests. It saves working directories, timestamps, hashed session/turn identifiers and optional process identity. Shared window records include workspace names and paths. It does not save prompt, answer or transcript text.

Hook setup preserves other hooks and saves private configuration backups under ~/.local/share/awake-vscode. Backups may contain your existing hook configuration.

Pre-release limitations

• Tested on Apple Silicon macOS with VS Code 1.142.0 and Codex extension 26.1007.21434 (bundled Codex 0.162.0-alpha.17.2).
• Codex main turns are tracked. Background subagents continuing after the main turn are not covered. Same-folder Codex CLI sessions also count.
• A missing completion event can leave activity active for up to two hours. Pause is an immediate override; use a timer for longer work.
• Terminal tracking needs VS Code shell integration. Commands already running when Awake activates cannot be reconstructed.
• Claude, Intel Macs in this initial package, remote windows, Windows, Linux and browser VS Code are unsupported.
• Keep the lid open. Awake does not unlock your Mac, override lock policy, prevent explicit sleep, or force sleep when work finishes.

Remove or reconnect

Run Awake: Remove Codex Integration before uninstalling Awake. Uninstalling alone does not remove external hooks. Removal disables the launcher and removes Awake's hook entries; backups and helper files remain for recovery.

Reinstalling intentionally keeps a removed integration disabled. Run Awake: Set Up Codex to reconnect it explicitly.

Feedback

Report a problem or read setup help. You can also use this listing's Q & A tab. Include Awake, VS Code, Codex and macOS versions, what happened, and how to reproduce it. Awake: Show Diagnostics can help; review paths and workspace names before sharing. Do not post credentials, conversation text or hook configuration backups.

Awake is an independent extension, not an OpenAI or Microsoft product. Licensed under MIT. Source hosting is currently private.