Compaction fails with: Error running remote compact task: Request blocked.
Open 💬 6 comments Opened Jul 10, 2026 by AcrylicShrimp
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.707.31428
What subscription do you have?
Pro plan
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
Compaction fails with:
Error running remote compact task: Request blocked.
What steps can reproduce the bug?
Feedback ID: 019f472f-e43f-77d1-aac2-1f3ce1cfc7d7
What is the expected behavior?
_No response_
Additional information
<img width="490" height="581" alt="Image" src="https://github.com/user-attachments/assets/195f7a29-e00b-4181-85d0-06906f028f26" />
<img width="163" height="56" alt="Image" src="https://github.com/user-attachments/assets/fb16e3d2-33c2-4086-8e7a-db55ed40d37f" />
<img width="507" height="274" alt="Image" src="https://github.com/user-attachments/assets/2e39a1c7-1e07-4726-8658-ade6aa044750" />
6 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Experienced the same problem ( in CLI ) today with all the 5.6 models, only affecting one of my sessions.
Temporarily switching to a 5.5 model and compacting there worked fine.
Compacting with a 5.6 model afterwards also worked fine.
Edit: Until normal prompts also started getting blocked. Guess it's back to 5.5.
Cross-referencing related
gpt-5.6Request blockedreports that may share the same root cause.Request blockedongpt-5.6-sol.Request blockedongpt-5.6.<|channel|>analysisis sufficient to triggerRequest blocked/invalid_request_bodyon allgpt-5.6-*models (luna/sol/terra). Earlier models (gpt-5-mini through gpt-5.5) all accept the same payload.Since your issue is compaction itself being blocked: compaction serializes conversation history into a text summary and sends it as input to the model. If that serialized text contains Harmony control-token markers (e.g.
<|channel|>analysisfrom assistant reasoning/thinking), thegpt-5.6input-side safety classifier may reject it — which would explain why compaction fails on 5.6 but works on 5.5.Your workaround (switch to 5.5, compact, switch back) is consistent with this: the 5.5 compaction produces a summary that strips or doesn't trigger the control-token pattern, after which 5.6 can process the cleaned summary. However, your edit noting that "normal prompts also started getting blocked" suggests the trigger text may persist in the thread's context even after compaction, eventually poisoning subsequent requests as well.
Related: #32177, #32533.
i see this error still having 21% context left
no change on restart with codex resume
I also received this error when working with codex on modifications to a llama.cpp jinja template for an open weights model, that channel marker was definitely in my context, as we'd been discussing the template logic. I asked for a change to the template at some point later and then the session died with every request blocked. I tried to compact, the compact operation was also blocked.
I second this. My requests consistently get blocked when I'm using codex to help me with a jinja template