[GH-ISSUE #169] bug: Codex Auto approval mode fails because `on-failure` is no longer supported #89

New issue

Closed

opened 2026-10-18 14:02:48 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-18 14:02:48 +00:00

Owner

Originally created by @AmarBego on GitHub (Jul 24, 2026).
Original GitHub issue: https://github.com/open-webui/computer/issues/169

Using Codex with approval mode Auto causes every chat request to fail.

Versions

Open WebUI Computer: v0.9.15 Docker image
Codex CLI: 0.145.0
Host: Ubuntu, Docker Compose

Error : Invalid request: unknown variant on-failure, expected one of untrusted, on-request, granular, never

Steps to reproduce

Configure an authenticated Codex agent profile.
Start a workspace chat using Codex.
Set approval mode to Auto.
Send any prompt.

cptr/utils/agents/codex.py currently maps Auto to the removed on-failure policy:
return {"ask": "on-request", "auto": "on-failure", "full": "never"}.get(value, "on-failure")

Codex 0.145.0 only accepts:

untrusted
on-request
granular
never

a workaround seems to be
Using approval mode Ask works because it maps to on-request.

Locally changing Auto and the fallback from on-failure to on-request also fixes the problem. so i guess map Auto to a currently supported Codex approval policy, likely on-request, and add a compatibility test covering the values accepted by current Codex app-server versions.

Originally created by @AmarBego on GitHub (Jul 24, 2026). Original GitHub issue: https://github.com/open-webui/computer/issues/169 Using Codex with approval mode **Auto** causes every chat request to fail. **Versions** - Open WebUI Computer: v0.9.15 Docker image - Codex CLI: 0.145.0 - Host: Ubuntu, Docker Compose **Error** : `Invalid request: unknown variant on-failure, expected one of untrusted, on-request, granular, never` Steps to reproduce 1. Configure an authenticated Codex agent profile. 2. Start a workspace chat using Codex. 3. Set approval mode to Auto. 4. Send any prompt. `cptr/utils/agents/codex.py` currently maps Auto to the removed `on-failure` policy: return {"ask": "on-request", "auto": "on-failure", "full": "never"}.get(value, "on-failure") Codex 0.145.0 only accepts: - untrusted - on-request - granular - never a workaround seems to be Using approval mode Ask works because it maps to on-request. Locally changing Auto and the fallback from on-failure to on-request also fixes the problem. so i guess map Auto to a currently supported Codex approval policy, likely on-request, and add a compatibility test covering the values accepted by current Codex app-server versions.

bsakaguchi closed this issue

2026-10-18 14:02:49 +00:00

bsakaguchi commented

2026-10-18 14:02:49 +00:00

Author

Owner

@owui-terminator[bot] commented on GitHub (Jul 24, 2026):

⚠️ Missing Issue Title Prefix

@AmarBego, your issue title is missing a categorising prefix (e.g. bug:, feat:, docs:).

Please update the title to lead with one of:

bug: bug report or error
feat: feature request or enhancement
docs: documentation issue
question: usage question
help: support request

Example: bug: Login fails when the password contains special characters

@owui-terminator[bot] commented on GitHub (Jul 24, 2026): # ⚠️ Missing Issue Title Prefix @AmarBego, your issue title is missing a categorising prefix (e.g. `bug:`, `feat:`, `docs:`). Please update the title to lead with one of: - **bug**: bug report or error - **feat**: feature request or enhancement - **docs**: documentation issue - **question**: usage question - **help**: support request Example: `bug: Login fails when the password contains special characters`

bsakaguchi commented

2026-10-18 14:02:49 +00:00

Author

Owner

@tjbck commented on GitHub (Aug 2, 2026):

Should be addressed!

@tjbck commented on GitHub (Aug 2, 2026): Should be addressed!

bsakaguchi referenced this issue

2026-10-18 14:04:22 +00:00

[PR #89] [MERGED] 0.7.4 #281