openai / openai/codex

Desktop Auto-review rejects 79,785-byte Google Drive batch update as over 200,000-byte review limit

Open
#46,094 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug sandbox tool-calls
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

On 2026-09-17, Codex desktop on macOS rejected a user-authorized google_drive.batch_update_spreadsheet call before execution with Guardian action exceeds the 200000-byte review limit. The tool arguments measured 79,785 UTF-8 bytes. The call would add one tab, write a header and 365 date rows, and set validation and formatting. The tool record showed failure at 0 ms; a metadata read confirmed no tab was created.

We cannot determine the size or composition of the full Auto-review input. Please clarify how this limit is measured, whether the documented /approve flow or an equivalent desktop flow applies to this failure, and the supported way to complete the reviewed operation. This differs from #44808, where the tool arguments themselves exceeded 200,000 bytes. No split or indirect retry has been attempted.

No spreadsheet ID, private project details, request payload, or logs are included.

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

Start by tracing the Auto-review handling for google_drive.batch_update_spreadsheet and the 200000-byte review limit, then inspect how the documented /approve flow applies to this failure. Verify how the input size is measured and identify the supported desktop completion path; done means the behavior and resolution are documented or corrected.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.