openai / openai/codex

Desktop browser: Runway file upload blocked by Auto-review; unclear supported recovery path

Open
#44,910 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app browser bug
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Summary

Browser automation for https://app.runwayml.com in the Codex desktop app on macOS stopped at a file-upload step after an Auto-review denial. Earlier browser operations in the same task had worked.

Observed behavior

  • A local PNG upload through the browser file chooser was rejected at setFiles with Browser Use rejected / Auto-review denied.
  • The agent was instructed not to retry through alternate browser surfaces or indirect execution and stopped.
  • The user did not see a separate approval prompt.
  • Signing in again and reverting a site permission from Always allow to Requires approval did not establish recovery.
  • A separate read-only plugin authentication check had succeeded; that is not evidence that browser automation was restored.
  • The exact initial cause remains unknown. This report describes earlier observations, not a fresh reproduction.

Environment

  • Codex desktop app on macOS, built-in browser
  • Approval reviewer: auto_review
  • Observed on 2026-09-11, Europe/Moscow
  • Exact app and OS versions: not yet verified

Feedback ID

019fa378-2b29-7b03-a411-2450276d33d1

The user explicitly authorized public publication of this error description and this feedback ID. No conversation transcript, source images, credentials, or account details are attached.

Requested clarification

  1. Is uploading a local image through the desktop built-in browser supported?
  2. Is this an expected restriction or a possible integration/approval-state error?
  3. What official, narrowly scoped recovery path is available in the desktop app if the denial was incorrect?
  4. Which additional sanitized diagnostics would help?

We are not requesting that security checks be disabled or bypassed.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files, tests, or entry points are identified. Start by reviewing feedback ID 019fa378-2b29-7b03-a411-2450276d33d1 and verifying whether local image uploads through the macOS built-in browser are supported; document the expected restriction or recovery path and the sanitized diagnostics needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
desktop, security
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.