Follow-up messages blocked

“Codex Desktop (Windows) – follow-up messages cannot be sent: "codex-home" query stuck in fetching state”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/16019/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Follow-up messages cannot be sent after first turn. On Windows Codex Desktop, the codex-home query stays stuck fetching and the composer shows "Loading…" or a permanent spinner.

Is this your bug?

File my report

Where: Windows desktop app
Error text: submitBlockReason: loading-local-config
Versions: 0.155.0 to 26.908.9136.0
Platforms: Windows

Related: Follow-up messages won't send

Not quite your bug?

Follow-up Send hangs3 people
Desktop requests expire queued after RPC stalls fill in-flight slots4 people
Follow-up messages cannot be sent40 people

Original reports2, newest first

Sep 22, 2026Windows desktop: composer permanently blocked after the first turn — submitBlockReason: loading-local-config while localWorkspaceMaterialization stays loading with no codex-home re-fetch (deadlock, no reload path in prod builds)On GitHub#47216
Sep 16, 2026Windows desktop 26.908: follow-up messages blocked, codex-home query stuck in fetching stateOn GitHub#45906