Codex desktop Allow Once permission blocks recurring browser monitoring

Product

Codex desktop on macOS

Problem

A heartbeat automation configured to monitor an already linked WhatsApp Web tab every five minutes cannot continue unattended because computer access repeatedly requires the user to choose Allow Once. The user has explicitly authorized the recurring workflow, but that grant does not persist for later heartbeat runs.

Expected behavior

Codex should offer a user controlled persistent permission that is narrowly scoped to the saved automation, connected browser profile, tab, and host. The user should be able to review and revoke that permission at any time.

Actual behavior

Only Allow Once is available or honored. A later scheduled run blocks again and requires the user to be present.

Impact

Continuous browser monitoring cannot function. Requiring a new click on every run defeats the purpose of a recurring automation.

Suggested improvement

Add an Allow for this automation choice with a clear scope, expiration, status, and revocation control. When access expires, show one actionable notice instead of prompting on every run.

Privacy

This report contains no account identifiers, contact names, medical details, or conversation content.

Start by locating Codex desktop's macOS permission handling and the heartbeat automation entry point; the payload does not name specific files or tests. Trace how Allow Once is requested and persisted for a linked browser tab. Done means a scoped, reviewable and revocable recurring permission works without prompting on every run, including expiration handling.