Repository navigation
Windows Desktop: Cannot create new Cloud Work task, send button stays disabled #49608
Description
Activity
Additional detail:
This issue started immediately after today’s ChatGPT Windows desktop app update. Before updating the client, creating new Cloud Work tasks worked normally on the same account and the same computer. After updating to version 26.928.21956, the send button remains disabled when attempting to create a new Cloud Work task, while all other behaviors described above remain unchanged.This suggests the issue may be a regression introduced in the latest Windows desktop client update.I can reproduce the same issue in ChatGPT Windows desktop app version 26.930.31730.
The Send button remains disabled when starting a new cloud Work chat, even with only
testentered, no project selected, and no attachments. Pressing Enter does nothing.Creating new cloud Work chats on the web works, and existing cloud conversations can be continued in the desktop app.
Switching models, restarting, reinstalling, and signing out and back in did not resolve the issue.
In-app feedback ID:
no-active-thread-01a1016c-65d0-7ab0-acb9-301108e5283dConfirming the same issue on 26.930.31730 / Windows 11 26H2 (26300.9550).
Repair and Reset did not resolve it.
Feedback IDs:- Broken new Work chat: no-active-thread-01a1051a-a780-7021-9164-e807dab2bef6
- Existing normal Chat: no-active-thread-01a10523-8f34-7fc0-9cfe-aeb854665f9a
Interestingly, /feedback also returned no-active-thread-... even from a functioning existing Chat.
Still reproducing on Windows ChatGPT Desktop 26.930.61225.
The issue only affects creating a new Work chat with “Run in the cloud” in the Windows app: the Send button remains disabled, both inside a Project and with no Project selected.
However, if I create the Cloud Work chat on the web first, I can open that same chat in the Windows app and continue sending messages normally.
So Cloud Work itself, account permissions, projects, and connectivity appear to be working; the problem seems specific to the Windows Desktop new Cloud Work creation/composer flow.I can reproduce the same issue on the latest ChatGPT Windows desktop app.
Environment- ChatGPT Windows app version: 26.1002.51308
- Release date shown in the app: October 7, 2026
Behavior
In the Windows desktop app, when I switch to Work and start a new Work conversation, I can type text into the composer, but the Send button remains disabled and cannot be clicked.
Regular Chat mode works normally in the same Windows app.
I also tested the same account in the ChatGPT web app: - Creating a new Work conversation on the web works normally
- I can send the first message successfully on the web
- After that, the same Work conversation appears in the Windows app
- I can then continue chatting normally in that existing Work conversation from the Windows app
So in my case, Work itself, account permissions, and existing Work conversations are working correctly. The problem appears to be specifically with starting/sending the first message of a new Work conversation from the Windows desktop app.
I also tried Resetting the ChatGPT app from Windows Settings, but the issue still occurs.
Reproduction steps
- Open the ChatGPT Windows desktop app.
- Switch from Chat to Work.
- Start a new Work conversation.
- Type any text, for example 123.
- The Send button stays disabled.
- Open ChatGPT on the web and create a new Work conversation.
- Send the first message successfully.
- Open that conversation in the Windows desktop app.
- The Windows app can now continue the same Work conversation normally.
Workaround
Create the Work conversation and send the first message from the web app, then continue the conversation in the Windows desktop app.
This seems to confirm that the issue is specific to the new Cloud Work task / initial message flow in the Windows client, rather than a general Work availability or account issue.
Reproduced on 2026-10-07 in the ChatGPT Windows desktop app. Local execution is affected too in my case.
Steps:
- Start a new Work conversation in the Windows app.
- Select either local execution or Run in the cloud.
- Enter
test.
Result: the Send button stays disabled with no error shown. This happens with both execution options.
With the same account, Work on the web sends and receives a reply, and regular Chat in the Windows app also sends and receives a reply. Existing Work conversations and new Codex tasks can be submitted and begin processing.
Restarting the app, restarting the PC, selecting a project, switching between local/cloud execution, and pausing other agent tasks did not resolve it.
I haven't verified the exact app build.
I have this issue when trying to run local (On My Computer), not cloud
I can still reproduce this issue on ChatGPT for Windows version 26.1002.52244.
The problem is specifically with starting a new cloud Work conversation in the Windows desktop app. Continuing an existing cloud conversation works.
Environment
- OS: Windows 11
- ChatGPT desktop app version: 26.1002.52244
- Selected model / reasoning level in the UI: GPT-6 Astra / Max
Reproduction and comparison tests
All tests were performed using the same account.
-
In the Windows app, start a new Work conversation, select cloud execution, and enter a simple prompt such as
1+1=?.- The Send button remains disabled.
-
Without changing the prompt or the selected model / reasoning level, switch the new conversation to local execution.
- The Send button immediately becomes enabled.
-
On the ChatGPT website, create a new cloud Work conversation and send the first message.
- The message sends successfully, and a response is received.
-
Open that same cloud conversation in the Windows desktop app and send a follow-up message.
- This also works: the message sends successfully, and a response is received.
Troubleshooting already attempted
- Updated the Windows app to 26.1002.52244.
- Signed out and signed back in.
- Used the Windows app Repair option — not Reset.
None of these resolved the issue.
Expected behavior
The Windows app should allow me to create a new cloud Work conversation and send its first message directly, without having to create it on the website first.
Current workaround
Create the cloud Work conversation and send the first message on the website, then continue the same conversation in the Windows app.
Could you confirm whether the previously released fix was intended to cover this specific cloud-only scenario? It remains reproducible on 26.1002.52244.
[Windows][26.1007.21434] Cannot create new Cloud Work conversations from Desktop, but existing Cloud Work works normally
Summary
I cannot create a new Cloud Work conversation from the ChatGPT Windows desktop app.
When I select “Run in the cloud”, I can type a prompt, but the Send button remains disabled and pressing Enter does not create the conversation.
However, this issue appears to affect only the creation of a new Cloud Work conversation from the Windows desktop app.
Cloud Work itself works normally once the conversation already exists.
Environment
- OS: Windows
- ChatGPT Desktop version: 26.1007.21434
- Release date shown in the app: October 9, 2026
- Plan: ChatGPT Plus
- The desktop app reports: “ChatGPT is up to date”
- Reproduced on: October 11, 2026
Steps to reproduce
- Open the ChatGPT Windows desktop app.
- Start a new Work conversation.
- Enter any prompt.
- Open the option for where the conversation should run.
- Select “Run in the cloud”.
- Try to send the first message.
Actual behavior
The Cloud option can be selected, but the Send button becomes/remains disabled.
Pressing Enter also does nothing.
As a result, a new Cloud Work conversation cannot be created from the Windows desktop app.
Expected behavior
After selecting “Run in the cloud”, I should be able to submit the first message and create a new Cloud Work conversation from the desktop app.
Tests I performed
I tested several related scenarios to narrow down the problem.
1. Local Work works normally
If I select “Run on your computer”, the Send button is enabled and I can create the Work conversation normally.
So creating a new Work conversation itself works.
2. Cloud Work works normally on the web
Using the same ChatGPT account on chatgpt.com, I can create a new Cloud Work conversation normally.
So my account appears to have access to Cloud Work.
3. Web-created Cloud Work syncs to Desktop
If I create a Cloud Work conversation on the web, it appears normally in the Windows desktop app.
4. Existing Cloud Work can be continued from Desktop
A Cloud Work conversation created on the web can be opened in the Windows desktop app.
I can send additional messages from the Windows app and receive responses normally.
So the Windows client is able to:
- load an existing Cloud Work conversation;
- sync it correctly;
- send messages to it;
- receive Cloud Work responses.
The failure appears to happen specifically when the Windows client tries to create the Cloud Work conversation for the first time.
5. The issue is not limited to Projects
I reproduced the issue both:
- inside a ChatGPT Project;
- outside of any Project.
6. Changing model / reasoning level does not fix it
I also tested different model/reasoning settings, including the default setting.
The behavior is unchanged.
Scope of the issue
Based on these tests, this does not appear to be a general Cloud Work failure.
The following path works:
Web
→ Create Cloud Work
→ Sync to Windows Desktop
→ Continue Cloud Work from Windows DesktopBut this path fails:
Windows Desktop
→ New Work
→ Run in the cloud
→ Send first message
→ Cannot create Cloud Work conversationSo the issue appears to be specifically related to:
Windows Desktop → Create new Cloud Work conversation
rather than Cloud Work execution, synchronization, or account access.
Additional information
The app is already updated to 26.1007.21434 and reports that no newer update is available.
I can provide screenshots / screen recordings showing:
- the current desktop app version;
- Local Work being sendable;
- Cloud Work being selected while the Send button remains disabled;
- a Cloud Work conversation created on the web being successfully continued from the Windows desktop app.
supplement
PS. The project named “基础聊天basic chat” was created on the ChatGPT web app, so it is a cloud-based ChatGPT Project rather than a local desktop project.
I used it specifically to verify whether this bug was related to where the Project was created.
The same problem still occurs there: from the Windows desktop app, I can select “Run in the cloud”, but I still cannot submit the first message and create a new Cloud Work conversation.
This suggests the issue is not caused by the Project being created locally on the desktop app.
What version of the Codex App are you using (From “About Codex” dialog)?
26.928.21956
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Windows 10
What issue are you seeing?
Description
In the ChatGPT Windows desktop app, I cannot create a new Cloud Work task.
When Work is set to run in the cloud, I can type normally in the prompt box, but the send button remains disabled/greyed out and the task cannot be started.
However, Cloud Work itself works correctly on my account.
Environment
Important observations
Troubleshooting already attempted
I have already reset the ChatGPT Windows app using Windows Settings.
The issue still occurs after the reset.
Workaround
Currently, I can:
So the problem appears to be specifically related to the new Cloud Work task creation flow in the Windows desktop client.
Additional information
When switching Work to local execution, the send button becomes enabled normally.
When switching to cloud execution for a new task, the send button remains disabled.
What steps can reproduce the bug?
Steps to reproduce
Actual behavior
The send button remains disabled even though text has been entered, so a new Cloud Work task cannot be created.
What is the expected behavior?
Expected behavior
The send button should become enabled after entering a prompt, and the new Cloud Work task should start normally.
Additional information
No response