[macOS desktop] Scoped permission grant still leaves credential stdin workflow blocked without an actionable approval

Finding: In an external report on the Codex desktop macOS app 26.930.61225 (bundled CLI 0.160.1, macOS 26.3.1 (a), workspace-write sandbox, granular approval policy), a write_stdin call to a waiting workspace-local PTY writer was rejected even after a scoped permission grant for that exact config file. The rejection message says approval is required by policy but that the granular sandbox_approval setting is false (https://github.com/openai/codex/issues/52759). Reported sequence: the user started a local Python configuration writer in a PTY with echo disabled. It waits for one JSON line and is meant to write a mode-0600 workspace-local config file. The permission tool returned an exact-path grant with scope turn. The write_stdin call was then rejected before the writer received any input. A fresh writer started after the grant produced the same rejection. No actionable approval prompt or explanation of the missing requirement appeared. Empty write_stdin reads from other running sessions still worked (https://github.com/openai/codex/issues/52759). The reporter also lists blockers that may be intended sandbox limitations. Scoped write requests for ~/Library/LaunchAgents, and for a single plist file, returned no filesystem grant. A direct generation test using the existing CLI ChatGPT login failed at startup with a readonly logs database error and an os error 1 (Operation not permitted) while initializing the in-process app-server client. The reporter asks that these be separated from the stdin rejection (https://github.com/openai/codex/issues/52759). Status: the issue is open. The only comment is an automated bot suggesting possible duplicates #52210, #51688 and #52517, and no maintainer has commented. The cause is therefore unconfirmed. It could be approval-state propagation, intended policy enforcement with poor UX, or both, which is the question the reporter poses. No workaround, fix commit or released fix appears in the supplied sources (https://github.com/openai/codex/issues/52759). Diagnostic reading, limited to the source: the error text points at the granular approval policy having sandbox_approval disabled, and the exact-path file grant did not change the outcome for write_stdin in this session. This is an inference from the report, not a confirmed cause. Limitations: this is a single external user report, not reproduced by KFA. Comment coverage is partial. Related issues were mentioned by the reporter but not supplied, so they are not used as evidence. No safe action is source-backed, so no solution is offered.