I only receive the response: {"detail":"Bad Request"}

### What version of the Codex App are you using (From “About Codex” dialog)? Version 26.803.41515 ### What subscription do you have? Max ### What platform is your computer? Win11 ### What issue are you seeing? I only get this both from the terminal as well as from the desktop app: Version 26.803.41515 <img alt="Image" width="804" height="339" src="https://private-user-images.githubusercontent.com/576897/633461753-134adbed-bcb8-42c6-b747-1374b6581ba2.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODYzMTY4NjgsIm5iZiI6MTc4NjMxNjU2OCwicGF0aCI6Ii81NzY4OTcvNjMzNDYxNzUzLTEzNGFkYmVkLWJjYjgtNDJjNi1iNzQ3LTEzNzRiNjU4MWJhMi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwODA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDgwOVQyMzAyNDhaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0yNDg2MDdiZmIxMWYzOTAyMzkxZTQ5MDFkYjVmMGJlNjcwYTA5MzI4MWYyZDQ2YjhhMTgwNGJmYTNiODhmZmVhJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZyZXNwb25zZS1jb250ZW50LXR5cGU9aW1hZ2UlMkZwbmcifQ.31rwb9MJfkwPC2YF8NmMiesyxogyUALujGjngnFOOME"> ### What steps can reproduce the bug? Feedback ID: 019fe803-afe8-7ce3-b990-568f290e3b16 ### What is the expected behavior? A response! ### Additional information It only seems to happen when working on the Blueprint app. It is keeping from from working!

I opened up a new Codex terminal window in my Blueprint repo and received:

...
• The built-in image tool is the right path here; it avoids the failing terminal bridge that previously surfaced {"detail":"Bad Request"}. I’m locating the existing deterministic kitchen/glass-door
reference canvases and will visually inspect them before sending two separate generation requests.

• Running Get-ChildItem -LiteralPath 'artifacts' -Directory | Where-Object { $_.Name -match 'kitchen|interior|unit8i|unit8j|unit8k|gallery' } | Select-Object FullName,LastWriteTime; Get-ChildItem
│ -LiteralPath 'artifacts' -Recurse -File -Include '*.png','appearance-job.json','view.json','assembly.json' | Where-Object { $_.FullName -match 'kitchen|interior|unit8i|unit8j|unit8k|
│ gallery' } | Select-Object FullName,Length,LastWriteTime | Sort-Object FullName

⚠ Automatic approval review approved (risk: low, authorization: high): This is a read-only inventory of local reference artifact names and metadata needed for the user-authorized image generation.

✔ Auto-reviewer approved codex to run Get-ChildItem -LiteralPath 'artifacts' -Directory | Where-Object { $_.Name -m... this time

• Ran Get-ChildItem -LiteralPath 'artifacts' -Directory | Where-Object { $_.Name -match 'kitchen|interior|unit8i|unit8j|unit8k|gallery' } | Select-Object FullName,LastWriteTime; Get-ChildItem
│ -LiteralPath 'artifacts' -Recurse -File -Include '*.png','appearance-job.json','view.json','assembly.json' | Where-Object { $_.FullName -match 'kitchen|interior|unit8i|unit8j|unit8k|gallery' } |
│ Select-Object FullName,Length,LastWriteTime | Sort-Object FullName
└
FullName
… +75 lines (ctrl + t to view transcript)
C:\dev\Blueprint\artifacts\unit8m-kitchen-to-glass-door-request-2026-08-09\references\structural-guidance.png

• Ran Get-Content -LiteralPath 'artifacts\unit8l-kitchen-request-2026-08-09\appearance-job.json'; Get-Content -LiteralPath
│ 'artifacts\unit8m-kitchen-to-glass-door-request-2026-08-09\appearance-job.json'
└ {
"contract": "blueprint-perspective-image-job/v3",
… +278 lines (ctrl + t to view transcript)
"output_file_name": "kitchen-to-glass-door.png"
}

• Viewed Image
└ artifacts\unit8l-kitchen-request-2026-08-09\references\editable-canvas.png

• Viewed Image
└ artifacts\unit8l-kitchen-request-2026-08-09\references\structural-guidance.png

• Viewed Image
└ artifacts\unit8m-kitchen-to-glass-door-request-2026-08-09\references\editable-canvas.png

• Viewed Image
└ artifacts\unit8m-kitchen-to-glass-door-request-2026-08-09\references\structural-guidance.png

⚠ Falling back from WebSockets to HTTPS transport. stream disconnected before completion: websocket closed by server before response.completed

■ {"detail":"Bad Request"}

› I received: "⚠ Falling back from WebSockets to HTTPS transport. stream disconnected before completion: websocket closed by server before response.completed"

■ {"detail":"Bad Request"}

› And now only received ■ {"detail":"Bad Request"}

■ {"detail":"Bad Request"}

having exact same issue. max, win11

having exact same issue. max, win11

I was using Codex to generate images and they were being made part of the context... so eventually there was no context left. This error is then thrown, which I guess, to sum up, means you're trying to use more context than you're allowed. I reworked how the images were created, to not be part of the context, and this helped clear the issue up.