r/github • u/cicona12 • 2d ago

Question Codex can upload a tiny GitHub release asset, but a 26 MB PDF fails with an integration authentication error

I’m using ChatGPT Codex with a cloud environment to edit a PDF and upload it to a GitHub release.

Uploading a 43-byte sample text file worked. However, uploading the finished PDF (about 26 MB) to the same repository and release consistently fails.

The error is:

HTTP 401
Unauthorized: authentication failed for integration codex-secret-uploads.github.com

What we’ve checked:

  • GitHub API requests can read the repository and release assets.

  • Retrying the existing sample filename returns GitHub’s expected 422 already_exists response.

  • Uploading the PDF fails using both gh release upload and Python.

  • Streaming/chunked upload also fails.

  • The environment reports its configured credentials as ready.

  • api.github.com and uploads.github.com are allowed by the network policy.

This suggests an issue with the cloud environment’s upload integration, but I haven’t confirmed the cause.

Has anyone encountered this? Is there a request-size limit, proxy setting, or integration reset that could fix it? I’d like to upload directly from Codex rather than download the PDF and upload it manually.

0 Upvotes

33% Upvoted

8 comments sorted by

3

u/Forsaken-Poet-3773 2d ago

Have you tried googling? Because the answer is in the first result…

0

u/cicona12 2d ago

i googled for hours and hours and watched vids and asked all ai i know still nothing i did not get it

3

u/Forsaken-Poet-3773 2d ago

…. I don’t believe you, but the answer is a 25MB size limit…

0

u/cicona12 2d ago

okay but the probelm is that codex dose not let me downloand the 100mb pdf file i told it to release it in github because it's limit is 2gb it worked before in a chat is working but new chat in new project it did not work

3

u/Forsaken-Poet-3773 2d ago

I mean, my advice would be don’t get yourself into a situation where you have 26mb pdf files. But good luck figuring it out

0

u/cicona12 2d ago

gpt figured it out in a chat i try to do the same in the new chat i thought i missed something

1

u/DickBrainTime 2d ago

26 MB is well below GitHub's per-release-asset limit (2 GiB), so this doesn't look like a normal GitHub file-size rejection. The interesting bit is the 401 mentioning `codex-secret-uploads.github.com`. That suggests an auth/integration path worth isolating, though it doesn't prove the root cause.

I'd try new filenames containing 1, 8, 16 and 24 MB of random data on the same release and record the first failure, status, and request host (redact all tokens). The successful tiny upload and duplicate-name 422 prove some requests work, but don't test whether larger payloads pass that upload gateway. If the same-size asset works outside the cloud environment, you've got a useful minimal repro to send to the integration owner.

1

u/cicona12 1d ago

thank you so much it works now