Repository navigation
Windows Desktop: Send button disabled after first completed Local Codex/Work turn (native + WSL) #46618
Description
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
- Open ChatGPT Windows Desktop.
- Start a new Local Codex or Local Work conversation.
- Send any prompt.
- Wait until Codex/Work fully completes the task and returns its response.
- Type a second message into the composer.
- The Send button remains disabled/grey.
- 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
Activity
github-actions commentedon Sep 19, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
apol1980 commentedon Sep 20, 2026
I can independently reproduce this on a newer Windows Desktop build.
Environment:
codex_work_desktop0.155.0-alpha.9.2gpt-6-astraC:\Worktest01a0bd90-e30c-7f52-92db-261f6ba9911dReproduction:
Antwoord alleen met OK.).OK.Rollout evidence:
task_completeis persisted normally (duration 5284 ms)user messagetask_startedRelevant metadata:
approval_policy: neversandbox_policy: danger-full-accessrate_limit_reached_type: null)This makes an approval wait unlikely for this reproduction and strongly localizes the failure to the Windows desktop composer/client state before the request reaches the Codex runtime.
I also reproduced the behavior in a minimal test directory, so it does not appear project-specific. The web version continues to work.
StructureAI2026 commentedon Sep 20, 2026
Update: The issue is currently no longer reproducing on my machine.
ChatGPT Desktop still reports version 26.915.31945 and “Check for Updates” says the app is up to date, so there was no visible desktop app update.
I have now successfully continued multiple Local Codex/Work conversations across several turns without the composer becoming disabled.
I have not changed the app version since the previous reproduction. I will continue testing and report if the issue returns.
I am leaving the issue open for now because the failure had previously returned repeatedly after appearing temporarily resolved.
Sirius9121 commentedon Sep 21, 2026
This issue has been happening on my computer on and off. Please report if any fixes are found.
sup3rson1c commentedon Sep 21, 2026
Hey me too over here, I can't send more than one message in a chat
alexcodeur commentedon Sep 24, 2026
Bonsoir @sup3rson1c
La solution que j'ai trouvé est de me positionner dans le champ texte.
Puis je vois le bouton d'envoi qui est grisé.
Alors je clique sur ma tête en bas à gauche et je me rend dans les réglages.
Une fois la dedans, je reviens en arrière et c'est tout bon, je peux à nouveau soumettre des messages et reprendre ma conversation.
Good evening @sup3rson1c,
The workaround I found is to click inside the text field first.
I can then see that the send button is grayed out. So I click on my profile picture in the bottom-left corner and go to Settings.
Once I’m there, I simply go back, and everything works again. I can submit messages and continue my conversation as usual.