What version of the Codex App are you using (From “About Codex” dialog)?

26.1007.2314.0

What subscription do you have?

Both existing and newly created Local Work and Local Codex conversations become unusable. Text can be entered into the message composer, but the Send button remains disabled/greyed out. This affects all local conversations and multiple projects. After fully terminating the desktop application processes and restarting the app, local sending temporarily recovers. However, the issue returns within approximately 30 seconds. Cloud Work and the standalone Codex CLI continue functioning normally.

What platform is your computer?

Windows x64

What issue are you seeing?

Both existing and newly created Local Work and Local Codex conversations become unusable.

Text can be entered into the message composer, but the Send button remains disabled/greyed out. This affects all local conversations and multiple projects.

After fully terminating the desktop application processes and restarting the app, local sending temporarily recovers. However, the issue returns within approximately 30 seconds.

Cloud Work and the standalone Codex CLI continue functioning normally.

What steps can reproduce the bug?

Open the Windows desktop application.

Select Work Local or Codex Local.

Open an existing project or create a new project.

Create a local conversation and type a message.

Observe that the Send button is disabled.

Fully exit the application and terminate residual desktop UI processes.

Reopen the application and observe temporary recovery.

Within approximately 30 seconds, the Send button becomes disabled again across local conversations.

The exact trigger for recurrence has not yet been identified.

What is the expected behavior?

No response

Additional information

[Windows] Local Work and Codex Send button disabled across all conversations — temporary recovery after process restart

Environment

• Platform: Windows x64

• Windows app package: OpenAI.Codex 26.1007.2314.0

• Desktop UI version: 26.1011.11113

• Package family: OpenAI.Codex_2p2nqsd0c76g0

• Affected modes: Work Local and Codex Local

• Unaffected modes: Work Cloud and standalone Codex CLI

• Date observed: October 13, 2026

Bug description

Both existing and newly created Local Work and Local Codex conversations become unusable.

Text can be entered into the message composer, but the Send button remains disabled/greyed out. This affects all local conversations and multiple projects.

After fully terminating the desktop application processes and restarting the app, local sending temporarily recovers. However, the issue returns within approximately 30 seconds.

Cloud Work and the standalone Codex CLI continue functioning normally.

Steps to reproduce

1. Open the Windows desktop application.

2. Select Work Local or Codex Local.

3. Open an existing project or create a new project.

4. Create a local conversation and type a message.

5. Observe that the Send button is disabled.

6. Fully exit the application and terminate residual desktop UI processes.

7. Reopen the application and observe temporary recovery.

8. Within approximately 30 seconds, the Send button becomes disabled again across local conversations.

The exact trigger for recurrence has not yet been identified.

Diagnostic findings

• CodexSandboxService.OpenAI.Codex: Running, Automatic startup, ExitCode 0

• Bundled codex.exe: running

• Computer Use runtime: running

• AppX re-registration completed without reported errors

• Windows Application Event Log search did not reveal matching application errors

• Standalone Codex CLI can authenticate, submit prompts and receive responses

Desktop log observations:

Event | Log A | Log B | Log C -- | -- | -- | -- configRequirements/read | 11 | 11 | 3 windowsSandbox/readiness | 2 | 2 | 1 method=turn/start | 0 | 0 | 0 turn-start config resolved | 0 | 0 | 0 transport error | 0 | 0 | 0 connection_closed | 0 | 0 | 0

Several configRequirements/read entries contain errorCode=null. No concrete configuration error was established.

The lack of turn/start matches in the inspected logs suggests that submission may be blocked before a backend turn begins, although logging differences cannot be ruled out.

Expected behavior

All available local conversations should accept messages normally after initialization and should remain usable without requiring application restarts.

Actual behavior

The composer accepts text, but the Send button is disabled without an actionable error message. Restarting provides only a temporary recovery.

Request

Please investigate Windows desktop composer state management, local session initialization, and the bundled Codex backend communication.

A fix that preserves local conversation history, projects, and configuration is strongly preferred.

Related reports: #45626, #46763, #46986.