macOS: Send button disabled in existing chats while voice input still works

Summary

In Codex Desktop on macOS, reopening a previously used chat leaves normal typed messages unable to send. Text appears in the composer, but the blue Send button remains dimmed/disabled. Even a short message such as "hello" cannot be submitted. Voice input can still continue the same chat.

Environment

• Codex Desktop: 26.911.61220
• Bundled Codex CLI/app-server: 0.155.0-alpha.2.6
• macOS, Apple Silicon
• Observed September 18, 2026

Reproduction

1. Open a previously used chat, including by switching away and returning.
2. Type a short follow-up message.
3. Try to submit it using the Send button.

Actual result

The text remains in the composer; the Send button is disabled and no typed message can be submitted. The failure also occurs without an active voice session. Voice input remains functional in the affected chat.

Expected result

An existing chat whose previous turn has finished should accept another typed message.

Local diagnostics

After a full app restart, logs for this affected chat show successful resume alongside:

latestTurnStatus=completed
markedStreaming=true

There are also "Conversation state not found" messages associated with the avatar overlay. These are correlations only; the exact cause has not been established.

Troubleshooting performed

• Multiple full app restarts did not resolve the problem.
• A reversible cache test was completed with the app closed: ten selected disk/code/GPU cache directories were renamed and retained as backups. The problem remained unchanged.
• Chat history, authentication data, client settings, and databases were not intentionally changed by the cache test.

Related reports

Windows reports describe closely matching symptoms; this is a macOS reproduction and does not establish an identical cause:

• https://github.com/openai/codex/issues/45305
• https://github.com/openai/codex/issues/45626

No conversation content, account identifiers, credentials, full logs, or local filesystem paths are attached.

No source file or test is named. First reproduce the issue in an existing chat, then trace the resumed-chat state and typed-message send eligibility using latestTurnStatus=completed and markedStreaming=true as comparison points; done means a resumed chat accepts a typed message and the behavior has regression coverage.