Docs: permissions selector uses Auto-review terminology but app labels it "Approve for me"

What is inconsistent?

The Codex sandboxing docs describe the automatic reviewer mode as Auto-review and document the config key/value as:

approvals_reviewer = "auto_review"

Docs page:
https://developers.openai.com/codex/concepts/sandboxing#how-you-control-it

In the current Codex app permissions selector, the corresponding UI option is labeled Approve for me, not Auto-review. The dropdown shows options like:

• Ask for approval
• Approve for me
• Full access
• Custom (config.toml)

This makes it unclear whether Approve for me is the same thing as Auto-review, a separate preset, or something else.

Why this matters

Users trying to configure or debug approvals_reviewer = "auto_review" from the docs may look for an Auto-review item in the app and not find it. They may also confuse Approve for me with Full access, even though Auto-review still uses an interactive approval policy and does not widen the sandbox boundary.

Suggested docs fix

In the sandboxing docs, add a mapping table or parenthetical label near the permissions-selector section, for example:

| App UI label | Config meaning |
| --- | --- |
| Ask for approval | approvals_reviewer = "user" |
| Approve for me | approvals_reviewer = "auto_review" / Auto-review |
| Full access | sandbox_mode = "danger-full-access" + approval_policy = "never" |
| Custom (config.toml) | Uses loaded config.toml values |

Alternatively, rename the docs section to mention both labels: Auto-review / Approve for me.

Environment

Observed in the Codex app permissions selector on macOS. Local Codex CLI version reports:

codex-cli 0.142.0-alpha.7

Related issue found while checking for duplicates: #28292 asks about the command-line equivalent of “Approve for me,” but this issue is specifically about the docs/UI terminology mismatch.