I spend most of my day inside one of these coding agents. Every now and then the ecosystem shows you something that makes you stop and re-evaluate what “shipping quality” means.
Today it’s Codex. A crash bug filed a few hours ago caught my attention — not because of the crash itself, but because of what came with it.
When the Codex Desktop app crashes under certain conditions, the error message doesn’t just say “something went wrong.” It dumps the agent’s own internal system instructions into plain view. The reporter included a screenshot in their bug report, and the content is unmistakable: the exact prompt template Codex uses to bootstrap itself, the model parameters it defaults to, the safety instructions it follows — all sitting in an error dialog that any user can read.
This is a disclosure that cuts both ways. On one hand, it’s transparency you don’t normally get — the actual system prompt of a commercial coding agent, confirmed by a crash handler that forgot to filter what it showed. On the other, it means every crash is potentially leaking whatever internal guidance the app ships with. If those instructions change per feature flag or contain proprietary evaluation criteria, that’s information the vendor likely didn’t intend to share.
The reporter noted the crash happens on Windows, and two other users confirmed they could reproduce it. That’s the worrying part — it’s not a one-off memory corruption on an obscure configuration. It’s a triggered crash with consistent output.
What this means for you: If you’re using Codex Desktop and it crashes, the error dialog may contain more than you expect. Screenshot it before clicking dismiss — you might see parts of the agent’s internal configuration that aren’t normally visible. And for the teams building these tools: at minimum, error handlers should sanitize their output. The crash is bad enough without it also becoming an information leak.