#13573·paperclip

Codex quota probe passes --ask-for-approval untrusted, rejected by current codex-cli (0.152+): Costs page quota card errors on every install

Author: vlad259Created Sep 17, 2026Updated Sep 17, 2026

Summary

The Codex quota probe spawns codex -s read-only -a untrusted app-server (packages/adapters/codex-local/src/server/quota.ts:473). Current @openai/codex releases no longer accept untrusted for --ask-for-approval, so the Costs page's provider quota card shows:

Codex app-server: error: invalid value 'untrusted' for '--ask-for-approval <APPROVAL_POLICY>' [possible values: on-request, never] For more information, try '--help'.; no local codex auth token

Environment

  • Paperclip 2026.831.1 (image rev 65ec059); the line is unchanged on master as of v2026.916.0.
  • Dockerfile:159 installs @openai/codex@latest unpinned. At our build (2026-09-02) that resolved to codex-cli 0.152.1, whose --help lists [possible values: on-request, never]. The workspace-vendored @openai/[email protected] still accepts untrusted, so the value was removed between 0.149 and 0.152.
  • No agent here uses the Codex adapter; the probe runs for every registered adapter regardless (services/quota-windows.tsfetchAllQuotaWindows), so the error appears on every install with a recent Codex CLI.

Suggested fix

  1. quota.ts:473: use -a never (the app-server is spawned read-only and only queried for rate limits, so no approval prompt is ever wanted), or omit the flag.
  2. Pin or floor @openai/codex in the Dockerfile so a CLI flag change cannot break the build silently.

Separately, when there is no ~/.codex/auth.json the card still reports "no local codex auth token" after the flag is fixed; that part is expected for API-key-only installs, but the two messages are concatenated so the actionable one is hidden behind the cosmetic one.

Happy to open a PR for (1) if useful.