Windows Desktop: Send button disabled after first completed Local Codex/Work turn (native + WSL)

Summary

On the new ChatGPT Windows Desktop app, Local Codex and Local Work conversations become unusable after the first completed response.

The first prompt works normally. Codex/Work completes the task and returns a response. After that, I can type a second message into the composer, but the Send button remains disabled/grey, so the second message cannot be submitted.

The issue is consistently reproducible across multiple projects and also in newly created conversations.

Environment

• OS: Windows
• ChatGPT Desktop version: 26.915.31945
• Codex/Workspace component version shown in Settings: 26.909.11814
• ChatGPT plan: Pro
• Affected: Local Codex and Local Work
• Not affected: Regular Chat and Work Cloud

Reproduction steps

1. Open ChatGPT Windows Desktop.
2. Start a new Local Codex or Local Work conversation.
3. Send any prompt.
4. Wait until Codex/Work fully completes the task and returns its response.
5. Type a second message into the composer.
6. The Send button remains disabled/grey.
7. The conversation can no longer be continued.

There is no visible "awaiting approval", "needs input", or other pending state.

Expected behavior

After the first run has completed, the composer should become ready again and allow the next user message to be submitted.

Actual behavior

The composer accepts text input, but the Send button remains disabled after the completed response.

The second user message therefore never reaches the Codex transcript.

Isolation / troubleshooting performed

I have tested all of the following:

• Regular Chat: works normally across multiple turns
• Work Cloud: works normally across multiple turns
• Local Work: affected
• Local Codex: affected
• Multiple existing local projects: affected
• Newly created local conversations: affected
• Windows-native agent environment: affected
• WSL agent environment: affected
• Restarted ChatGPT: no change
• Windows App Repair: no change
• Windows App Reset: no change
• Complete uninstall and reinstall of ChatGPT Desktop: no change

OpenAI Support specifically suggested switching the Agent Environment from Windows-native to WSL as a workaround.

I switched to WSL, fully restarted the application, waited for the Codex WSL environment to initialize, and reproduced exactly the same issue.

In the WSL test, the first Codex task ran successfully, including SSH access to a VPS, and returned a complete response. Immediately afterward, the second message could be typed but could not be submitted because the Send button remained disabled.

Session ID

Clean minimal reproduction session:

01a0b8d5-1091-7643-96c3-9239d5295676

In this session, the first user prompt was "Antworte nur mit Hallo".

Codex responded "Hallo", and the transcript shows the turn completing successfully with a task_complete event.

There is no pending approval or input request after the task completion.

The UI nevertheless does not allow the next user message to be submitted.

Additional information

This is severely impacting my work because I use Local Codex / Local Work for software development, local repositories, PowerShell/terminal operations, SSH, VPS administration, and deployments.

OpenAI Support asked me to file this Codex bug report and provide the session transcript and sandbox logs.

I can provide additional reproduction sessions, screenshots, logs, or diagnostics if needed.

sandbox.2026-09-19.log
sandbox.log

rollout-2026-09-19T09-43-11-01a0b90c-6260-7b03-8072-dd9ab5c85fdf.zip

Start by reproducing the second-turn failure in a Windows Local Codex or Local Work conversation using the minimal session described in the issue. Review the attached sandbox logs and rollout archive around the completed task and disabled composer state. Done means the composer enables and submits a second message after the first task completes in both native Windows and WSL environments.