open-webui/computer

Fork 0

mirror of https://github.com/open-webui/computer.git synced 2026-11-05 01:17:24 +00:00

[GH-ISSUE #276] bug:cptr 0.9.21 ignores `danger-full-access` for Codex #188

New issue

Open

opened 2026-10-18 14:03:40 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-18 14:03:40 +00:00

Owner

Originally created by @Step-MS on GitHub (Sep 13, 2026).
Original GitHub issue: https://github.com/open-webui/computer/issues/276

Environment

cptr 0.9.21
Codex running inside a Docker container
Open WebUI using cptr
Codex profile configured with danger-full-access

Expected behavior

When the Codex profile is configured with danger-full-access, cptr should
start Codex with that sandbox mode, for example:

codex exec --sandbox danger-full-access

Actual behavior

The Codex start path appears to map the configured approval mode to
workspace-write, even when danger-full-access is configured. The relevant
behavior appears equivalent to:

def _sandbox_for_approval(value: str) -> str:
    if value == "ask":
        return "read-only"
    return "workspace-write"

As a result, Codex starts Bubblewrap. When cptr itself runs inside Docker,
this causes nested-sandbox failures and write errors.

A direct invocation of codex exec --sandbox danger-full-access works
correctly in the same container, which suggests that the problem is in the
cptr Codex launch path rather than Docker or Codex itself.

Workaround

I patched the cptr Codex launch path so that danger-full-access is passed
through unchanged. After that change, Open WebUI works correctly and Codex no
longer starts the nested Bubblewrap sandbox.

Request

Could you confirm whether this behavior is intentional? If not, please fix the
sandbox/approval mapping so that danger-full-access is respected and passed
to Codex unchanged.

Beim Kopieren die äußeren vier Backticks am Anfang und Ende weglassen.

Originally created by @Step-MS on GitHub (Sep 13, 2026). Original GitHub issue: https://github.com/open-webui/computer/issues/276 ## Environment - cptr 0.9.21 - Codex running inside a Docker container - Open WebUI using cptr - Codex profile configured with `danger-full-access` ## Expected behavior When the Codex profile is configured with `danger-full-access`, cptr should start Codex with that sandbox mode, for example: ```text codex exec --sandbox danger-full-access ``` ## Actual behavior The Codex start path appears to map the configured approval mode to `workspace-write`, even when `danger-full-access` is configured. The relevant behavior appears equivalent to: ```python def _sandbox_for_approval(value: str) -> str: if value == "ask": return "read-only" return "workspace-write" ``` As a result, Codex starts Bubblewrap. When cptr itself runs inside Docker, this causes nested-sandbox failures and write errors. A direct invocation of `codex exec --sandbox danger-full-access` works correctly in the same container, which suggests that the problem is in the cptr Codex launch path rather than Docker or Codex itself. ## Workaround I patched the cptr Codex launch path so that `danger-full-access` is passed through unchanged. After that change, Open WebUI works correctly and Codex no longer starts the nested Bubblewrap sandbox. ## Request Could you confirm whether this behavior is intentional? If not, please fix the sandbox/approval mapping so that `danger-full-access` is respected and passed to Codex unchanged. Beim Kopieren die äußeren vier Backticks am Anfang und Ende weglassen.

bsakaguchi commented

2026-10-18 14:03:40 +00:00

Author

Owner

@owui-terminator[bot] commented on GitHub (Sep 13, 2026):

⚠️ Missing Issue Title Prefix

@Step-MS, 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 (Sep 13, 2026): # ⚠️ Missing Issue Title Prefix @Step-MS, 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 referenced this issue

2026-10-18 14:03:47 +00:00

[GH-ISSUE #293] bug: user-facing error discards the provider's reason, only shows "Provider returned error" #206

No labels

enhancement

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

open-webui/computer#188

No description provided.

Rows
Columns

[GH-ISSUE #276] bug:cptr 0.9.21 ignores danger-full-access for Codex #188