Error

[JustElC]

Whenever I use this app, I get this error message at any time {"detail":"Bad Request"} (it could happen after 1 minute or 2 hours). I use Cloudflare WARP. Could that be causing the error?

[Leay15]

Sorry for the delay, @JustElC.

It could be, but based on the symptoms, I'd suspect the CLI/network layer more than the Linux app itself.

That {"detail":"Bad Request"} looks like a raw HTTP response bubbling up from lower layers, not a native UI error. In this fork, the app depends on the Codex CLI at runtime, so if the CLI, the session, or the connection to the backend gets into an invalid state, the app will likely just surface that response.

Cloudflare WARP could definitely be a contributing factor, especially if this isn't just consumer WARP but WARP/Zero Trust with inspection, proxying, or some other network policy in the middle. What makes me doubt that this is purely a Linux UI bug is that it happens "at any time," whether after 1 minute or 2 hours. That sounds more like a streaming, session, or network issue than a deterministic frontend problem.

My root-cause guess, in order of likelihood, would be:

an issue in the app -> Codex CLI -> backend communication path
interference from WARP, proxying, TLS inspection, or streaming traffic handling
much less likely: a Linux-specific UI bug
The most useful way to isolate it would be to test:

whether it still happens with WARP disabled
whether it also happens when using the Codex CLI directly outside the app
whether there's anything relevant in ~/.cache/codex-desktop/launcher.log
and in ~/.local/state/codex-update-manager/service.log
If it also happens in the CLI without the app involved, then the root cause is very likely not this Linux fork itself, but something further downstream, most likely related to the CLI, network, or backend.

[JustElC]

Its like a problem on OpeAI servers, I create a new chat and its fix up

[Leay15]

@JustElC perfect, I'll close this issue but feel you free for opening another if needed :)