Start queued local tasks when the Mac is plugged in and idle

What variant of Codex are you using?

Codex App on macOS.

What feature would you like to see?

Allow an explicitly queued local task to start when selected machine conditions are met.

For example: "Run the full test suite when my Mac is connected to power and has had no keyboard or mouse activity for ten minutes."

This would help users defer local builds, tests, and renders without choosing a fixed start time or watching the machine manually.

Proposed interaction design

Add When this Mac is ready as a timing option for a one-time local task in Scheduled. Preserve the task's prompt, project, and execution environment. Let the user select external power, an inactivity duration, or both.

Full test suite                              Waiting

✓ Connected to power
· Inactive for 10 minutes              4 / 10 minutes

[Run now]       [Edit conditions]             [Cancel]

After Queue task, show the unmet conditions in the task row. Evaluate readiness locally without starting an agent turn just to check power or inactivity.

Repeated condition events must not create another run for an item that has already started. After a restart, reconcile an uncertain start with the existing run before retrying.

Initial scope and interface details

Start with one-time local tasks. The Mac must be awake and Codex must be running for a queued task to start.

Reuse Codex's existing typography, controls, and status treatments. Status needs text as well as color, keyboard access, and a clear primary action appropriate to the current state. The layout and copy above are proposals for discussion.

Additional information

Iverson's WorkTool already provides scheduled prompts and keep-awake controls. This proposal adds machine conditions as the trigger for starting explicitly queued work.

No files, tests, or code entry points are named in the issue. Start by reviewing the proposed Scheduled interaction and the one-time local-task scope, then trace the existing task queuing, execution, and permission flow. Done means queued tasks persist, wait for the selected power or inactivity conditions, expose Run now and Cancel, and avoid duplicate starts after events or restart.