openai / openai/codex

"Never ask" silently blocks Messages approval prompts under Full Access

Open
#42,139 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app automations enhancement sandbox
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Correction: I initially misdiagnosed this as a per-task permission problem.

Codex treats sandbox access and approval prompting as separate settings. My configuration was:

sandbox_mode = "danger-full-access"
approval_policy = "never"

I read never as “approve everything.” It actually prevents approval prompts from appearing. Messages therefore failed with Read access was not approved.

Changing only approval_policy to on-request, while keeping sandbox_mode = "danger-full-access", fixes interactive Messages approval.

The remaining product issue is clarity and unattended behavior:

  • The UI should explicitly say that “Never” means “do not ask; approval-gated actions fail.”
  • Scheduled heartbeats run non-interactively, so a new Messages conversation still cannot obtain its first read approval. Previously approved conversations continue to work.

Environment: macOS, Codex CLI 0.151.0-alpha.7.2, Messages plugin 1.0.1000919.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how the CLI presents approval_policy choices and how scheduled heartbeats request access for new Messages conversations. Done means the UI clearly explains that “Never” suppresses prompts and approval-gated actions fail, while unattended behavior for a new conversation is defined or fixed.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
authorization, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.