Stream error : unexpected status 413 Payload Too Large (with 92% context left)

Resolved 💬 3 comments Opened Aug 29, 2025 by ceoz-0 Closed Nov 2, 2025

What version of Codex is running?

0.27.0 the same happens on 0.25.0 and 0.26.0

Which model were you using?

GPT-5 Medium and High

What platform is your computer?

Linux 6.16.3-lqx1-1-lqx x86_64 unknown

What steps can reproduce the bug?

Simply after GPT-5 try to read a small snippet of the file, it will start flooding with 413 errors, retrying continuously, non stop.

What is the expected behavior?

It should probably return a concise error, for either, authentication timeout (which is my main guess here), or how the payload exceeded the limit : was it in tokens ? what paload ? was it related to a MCP call ?

What do you see instead?

⚠  stream error: unexpected status 413 Payload Too Large: <html>
<head><title>413 Request Entity Too Large</title></head>
<body>
<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>cloudflare</center>
<script>(function(){function c(){var b=a.contentDocument||a.contentWindow.document;if(b){var
d=b.createElement('script');d.innerHTML="window.__CF$cv$params={r:'976d8e683a2be1ab',t:'MTc1NjQ4NjM1MC4wMDAwMDA='};var
a=document.createElement('script');a.nonce='';a.src='/cdn-cgi/challenge-platform/scripts/jsd/
main.js';document.getElementsByTagName('head')[0].appendChild(a);";b.getElementsByTagName('head')[0].appendChild(d)}}if(document.body){var
a=document.createElement('iframe');a.height=1;a.width=1;a.style.position='absolute';a.style.top=0;a.style.left=0;a.style.border='none';a.styl
e.visibility='hidden';document.body.appendChild(a);if('loading'!
==document.readyState)c();else if(window.addEventListener)document.addEventListener('DOMContentLoaded',c);else{var
e=document.onreadystatechange||function(){};document.onreadystatechange=function(b){e(b);'loading'!
==document.readyState&&(document.onreadystatechange=e,c())}}}})();</script></body>
</html>
; retrying 2/5 in 402ms…

Additional information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗