Activity

1. Plantain

   added

   extensionIssues related to the VS Code extensionIssues related to the VS Code extension

   on Feb 11, 2026
2. etraut-openai

   added

   contextIssues related to context management (including compaction)Issues related to context management (including compaction)

   on Feb 11, 2026
3. etraut-openai

   marked Error running remote compact task: unexpected status 413 Payload Too Large #11478 as a duplicate of this issue on Feb 15, 2026
4. etraut-openai

   marked Error running remote compact task: unexpected status 413 Payload Too Large #11863 as a duplicate of this issue on Feb 15, 2026
5. tomzlabs commented on Feb 23, 2026

   

   tomzlabs

   on Feb 23, 2026

   More actions

   Error running remote compact task: unexpected status 413 Payload Too Large: <title>413 Payload Too Large</title>

   413 Payload Too Large

   ---

   cloudflare , url: https://chatgpt.com/backend-api/codex/responses/compact, cf-ray: 9d2276fa7aa45aac-MEL
6. nbarbettini commented on Feb 25, 2026

   

   nbarbettini

   on Feb 25, 2026

   More actions

   I hit this with Codex CLI (not an IDE integration). Agent halted unexpectedly with 413 Payload Too Large, and any attempt to continue failed with 413. Compaction also failed with 413. thread ID 019c8df6-36df-79f3-99df-30d0e7fe6697
7. etraut-openai

   marked Codex IDE extension fails on long-lived thread with Error running remote compact task: 413 Payload Too Large #12874 as a duplicate of this issue on Feb 26, 2026
8. Code-Cats commented on Mar 13, 2026

   

   Code-Cats

   on Mar 13, 2026

   More actions

   I’m also hitting this consistently in ChatGPT Codex.

   Symptoms:

   • The conversation enters “auto compact / compress background” state.
   • Every subsequent message retriggers compaction.
   • Restarting the app or sending a new message in the same thread does not recover it.
   • The request fails with Cloudflare 413 on:
     https://chatgpt.com/backend-api/codex/responses/compact

   Observed error:
   Error running remote compact task: unexpected status 413 Payload Too Large:

   <title>413 Payload Too Large</title>

   413 Payload Too Large

   ---

   cloudflare

   cf-ray: 9db96b4fa9ef40fc-SIN

   What makes this especially bad:

   • Once a thread gets into this state, it appears permanently stuck.
   • Even short follow-up messages fail because compaction is retried first.
   • The only workaround is starting a brand new conversation and manually summarizing context.

   Expected behavior:

   • Compaction should chunk, trim, or otherwise bound payload size before sending.
   • If compaction fails, the thread should still remain usable instead of becoming unrecoverable.
   • Ideally the client should detect oversized compaction payloads and fall back to a smaller summary strategy automatically.

   If useful, I can provide screenshots of the UI state showing “auto compressing background information” immediately before the 413.

   👍React with 👍3Reacted by Maxim Krouk, ghpark-epi and Alvin Zhang
9. etraut-openai

   added

   bugSomething isn't workingSomething isn't working

   on May 14, 2026
10. Chi-Shan0707 commented on Jun 14, 2026

    

    Chi-Shan0707

    on Jun 14, 2026

    More actions

    I hit the same problem when trying to use Codex Cli to analyze some png files. When dealing with about less than 50 photos, it works. But it always failed if it tried to handle about 100 photos in a conversation.
11. etraut-openai commented on Jun 29, 2026

    

    etraut-openai

    on Jun 29, 2026

    Contributor

    More actions

    Thanks for reporting this problem. Until recently, Codex used a separate endpoint and server-side logic for compaction. We recently switched to a more robust approach where the compaction logic is moved locally using the same endpoint as normal turns. This eliminates "remote compaction" errors and increases the stability and reliability of compaction operations. If you see further problems with compaction, please use /feedback and open a new bug report.
12. etraut-openai

    closed this as completedon Jun 29, 2026