›_ Codex Issues
Codex Issues / #34499

Cannot create a local Work chat inside a ChatGPT Project (Windows Desktop App)

Open 💬 17 comments Opened Jul 21, 2026 by Paul722
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

26.715.61943 (released July 21, 2026)

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

What issue are you seeing?

When I try to create a Work chat inside an existing ChatGPT Project, I immediately receive errors such as:

  • "Could not sync ChatGPT project context"
  • "Could not use this project for a local chat"

The Work chat is not created.

What steps can reproduce the bug?

Feedback ID: 019f83d4-3c04-78a2-a4ce-3f1ff9273b23

What is the expected behavior?

A Work chat should be created inside the existing ChatGPT Project and retain access to the selected local folder. A Project should be able to contain one or more Work chats with access to local development folders.

Additional information

The problem occurs only when creating a local Work chat inside an existing Project.

Environment:

  • Windows Desktop App
  • ChatGPT Plus account
  • Codex App version 26.715.61943
  • Codex extension in VS Code works correctly
  • Local folder access works outside Projects

Could you please confirm whether this is a known issue or a bug? Screenshots showing the error can be attached.

View original on GitHub ↗

17 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #33888

Powered by Codex Action

Yemvis · 1 month ago

I can reproduce the same issue on the Windows desktop app.

Reproduction:

  1. Open an existing ChatGPT Project.
  2. Choose New local chat.
  3. Select On my computer.
  4. Choose a local folder.
  5. When prompted to use the Project context locally, click Add project.
  6. The operation fails with either:
  • Could not sync ChatGPT project context
  • Could not use this project for a local chat

Restarting the app and repeating the flow does not help. A standalone local chat outside the ChatGPT Project works, so local folder access itself is not the problem.

This is particularly confusing because the UI explicitly offers New local chat inside the Project and walks the user through the Add project flow. The expected result is a chat that keeps the Project instructions/files while executing on the local computer. Instead, the chat is never created, which blocks local tasks such as SSH and terminal work that depend on the Project context.

Please prioritize this regression or provide a supported workaround that preserves the ChatGPT Project context.

Paul722 · 1 month ago

Hi,

thanks for your message. I think I found the cause of the issue.

The problem does not seem to be the local folder itself, and Codex Work
also works in general. The issue seems to happen when a Work/local chat is
created from a ChatGPT Project without selecting the local working folder
during chat creation.

In my case, Work chats without the project worked fine. But Work chats from
the project failed with:

Could not sync ChatGPT project context
Could not use this project for a local chat

The fix was not just adding the folder path to the project instructions.
That only gives the model textual information; it does not grant technical
file access.

The important step is:

When creating the new Work/local chat, select or attach the local working
folder immediately during creation. After doing that, the same folder
access test worked.

So the practical rule seems to be:

When starting a Work/local chat from a ChatGPT Project, attach the local
folder right away during chat creation. Do not rely only on project
instructions that mention the path.

Best,
Paul

Am Mi., 22. Juli 2026 um 04:17 Uhr schrieb walter_paiva <
@.***>:

Yemvis left a comment (openai/codex#34499) <https://github.com/openai/codex/issues/34499#issuecomment-5041068420> I can reproduce the same issue on the Windows desktop app. Reproduction: 1. Open an existing ChatGPT Project. 2. Choose New local chat. 3. Select On my computer. 4. Choose a local folder. 5. When prompted to use the Project context locally, click Add project. 6. The operation fails with either: - Could not sync ChatGPT project context - Could not use this project for a local chat Restarting the app and repeating the flow does not help. A standalone local chat outside the ChatGPT Project works, so local folder access itself is not the problem. This is particularly confusing because the UI explicitly offers New local chat inside the Project and walks the user through the Add project flow. The expected result is a chat that keeps the Project instructions/files while executing on the local computer. Instead, the chat is never created, which blocks local tasks such as SSH and terminal work that depend on the Project context. Please prioritize this regression or provide a supported workaround that preserves the ChatGPT Project context. — Reply to this email directly, view it on GitHub <https://github.com/openai/codex/issues/34499?email_source=notifications&email_token=AMO6HSJ477QR53ABBPG6ZNL5GAP3TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBUGEYDMOBUGIYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5041068420>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMO6HSMS7WV6D6DNX7FM6I35GAP3TAVCNFSNUABFKJSXA33TNF2G64TZHM4TMNJUGE2TMNBZHNEXG43VMU5TIOJTG4ZDSOJSG43KC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AMO6HSKPK2NJ5RI4IGG4QEL5GAP3TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBUGEYDMOBUGIYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AMO6HSPRBXJXTWNGMMUIWKD5GAP3TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBUGEYDMOBUGIYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: @.***>
Paul722 · 1 month ago

Thanks, this matches my experience exactly.

The confusing part is that standalone local chats work, and creating a new
local project with a folder selected immediately also works. The failure
happens when trying to create a new local chat from an existing ChatGPT
Project and then adding the project context locally.

I also have older project-related Work/local chats that can still access
local files after permission is granted, but I cannot reliably reproduce
that setup anymore. This makes it unclear whether the behavior changed in
the Desktop app or whether there are now two different project/local-chat
flows with different capabilities.

A supported workaround that preserves both ChatGPT Project context and
local folder access would be very helpful.

Am Mi., 22. Juli 2026 um 04:17 Uhr schrieb walter_paiva <
@.***>:

Yemvis left a comment (openai/codex#34499) <https://github.com/openai/codex/issues/34499#issuecomment-5041068420> I can reproduce the same issue on the Windows desktop app. Reproduction: 1. Open an existing ChatGPT Project. 2. Choose New local chat. 3. Select On my computer. 4. Choose a local folder. 5. When prompted to use the Project context locally, click Add project. 6. The operation fails with either: - Could not sync ChatGPT project context - Could not use this project for a local chat Restarting the app and repeating the flow does not help. A standalone local chat outside the ChatGPT Project works, so local folder access itself is not the problem. This is particularly confusing because the UI explicitly offers New local chat inside the Project and walks the user through the Add project flow. The expected result is a chat that keeps the Project instructions/files while executing on the local computer. Instead, the chat is never created, which blocks local tasks such as SSH and terminal work that depend on the Project context. Please prioritize this regression or provide a supported workaround that preserves the ChatGPT Project context. — Reply to this email directly, view it on GitHub <https://github.com/openai/codex/issues/34499?email_source=notifications&email_token=AMO6HSJ477QR53ABBPG6ZNL5GAP3TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBUGEYDMOBUGIYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5041068420>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMO6HSMS7WV6D6DNX7FM6I35GAP3TAVCNFSNUABFKJSXA33TNF2G64TZHM4TMNJUGE2TMNBZHNEXG43VMU5TIOJTG4ZDSOJSG43KC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AMO6HSKPK2NJ5RI4IGG4QEL5GAP3TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBUGEYDMOBUGIYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AMO6HSPRBXJXTWNGMMUIWKD5GAP3TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBUGEYDMOBUGIYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: @.***>
uooing · 1 month ago

Same issue on a newer build — still reproducing as of 2026-07-23.

Environment:

  • App build: 26.715.72359 (released 2026-07-22) — newer than the 26.715.61943 in the original report
  • Store package version: 26.715.10079.0
  • Platform: Windows, Korean UI
  • Plan: ChatGPT Plus

Errors (identical, shown immediately, chat is not created):

  • "Could not sync ChatGPT project context"
  • "이 프로젝트를 로컬 작업에 사용할 수 없습니다"

(Korean UI string, equivalent of "Could not use this project for a local chat")

Repro:

  1. Open a Project in the Windows desktop app
  2. New Task inside the Project
  3. Set mode to Work
  4. Both errors appear instantly

Scope confirmed:

  • Fails ONLY inside a Project. Work mode works normally in a chat outside Projects.
  • Same account works correctly on chatgpt.com (web).

Tried with no effect: full reinstall, app reset, sign out/in, Windows Defender exclusion.

Feedback ID: no-active-thread-019f8ed6-2d1c-7180-abe0-ff5c98948fed

Paul722 · 1 month ago

it is really strange. In the same projekt I could create a workchat. But
two minutes later it didn't work anymore. But there is a way around. Crate
a new project. *By creating it you should click on the folder you want to
use. It werks well. But i comes with problem that you can
notintroduce context for your project. *

Am Do., 23. Juli 2026 um 14:05 Uhr schrieb uooing @.***

:
uooing left a comment (openai/codex#34499) <https://github.com/openai/codex/issues/34499#issuecomment-5058169940> Same issue on a newer build — still reproducing as of 2026-07-23. Environment: - App build: 26.715.72359 (released 2026-07-22) — newer than the 26.715.61943 in the original report - Store package version: 26.715.10079.0 - Platform: Windows, Korean UI - Plan: ChatGPT Plus Errors (identical, shown immediately, chat is not created): - "Could not sync ChatGPT project context" - "이 프로젝트를 로컬 작업에 사용할 수 없습니다" (Korean UI string, equivalent of "Could not use this project for a local chat") Repro: 1. Open a Project in the Windows desktop app 2. New Task inside the Project 3. Set mode to Work 4. Both errors appear instantly Scope confirmed: - Fails ONLY inside a Project. Work mode works normally in a chat outside Projects. - Same account works correctly on chatgpt.com (web). Tried with no effect: full reinstall, app reset, sign out/in, Windows Defender exclusion. Feedback ID: no-active-thread-019f8ed6-2d1c-7180-abe0-ff5c98948fed — Reply to this email directly, view it on GitHub <https://github.com/openai/codex/issues/34499?email_source=notifications&email_token=AMO6HSJG6F44BPHKRVFWWVL5GH5QLA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBVHAYTMOJZGQYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5058169940>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMO6HSN63N73YAHCJSTSCQL5GH5QLAVCNFSNUABFKJSXA33TNF2G64TZHM4TMNJUGE2TMNBZHNEXG43VMU5TIOJTG4ZDSOJSG43KC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AMO6HSP3Z5WCG6DUU7SIM3L5GH5QLA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBVHAYTMOJZGQYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AMO6HSMU24RKX3ALQKQC3635GH5QLA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBVHAYTMOJZGQYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: @.***>
SilentCogitator · 1 month ago

Same issue.
When I try to create a Work chat inside an existing ChatGPT Project, I immediately receive errors such as:

"Could not sync ChatGPT project context"
"Could not use this project for a local chat"
The Work chat is not created.

Fresh Windows 11 install.

Chat GPT:

Version 26.715.72359

Released 22 Jul 2026

cata078 · 1 month ago

I can confirm the same issue on Windows.

Environment:

  • Codex App version: 26.721.4979.0
  • Windows desktop application
  • The issue affects multiple existing ChatGPT Projects, not only one project.
  • Existing conversations remain visible, but creating a new local Work chat inside any ChatGPT Project fails.

Exact errors:

  • Could not sync ChatGPT project context
  • Could not use this project for a local chat

Troubleshooting already completed:

  • Completely closed the application and verified in Task Manager that no processes remained
  • Restarted the application
  • Tested multiple ChatGPT Projects
  • Signed out and signed back in
  • Checked Microsoft Store for updates; none were available
  • Used the Windows Repair option for the application
  • Retested after Repair

The issue still persists.

In my case, the problem became apparent after the OpenAI service disruption on July 25, 2026. During that period, I was working on an existing project and also experienced a project conversation/task no longer appearing where expected.

In-app feedback was submitted with session logs.

Feedback ID: 019f9a91-3daf-7fc1-8a8e-1752353bc596

I can provide screenshots showing both errors if needed.

Trippinlefty · 1 month ago

I can confirm this issue is still present on a newer desktop build and wanted to share some additional testing that may help narrow down the root cause.

Environment

  • OS: Windows 11
  • Plan: ChatGPT Plus
  • Desktop App: OpenAI.Codex 26.721.4979.0

Testing Performed

| Test | Result |
|------|--------|
| Create a Work chat outside a ChatGPT Project | ✅ Works |
| Open an existing Project-backed Work chat | ✅ Works |
| Create a new Work chat inside an existing Project | ❌ Fails |
| Create a brand-new empty Project, then create a Work chat | ❌ Fails |
| Sign out and back in | ❌ No change |
| Restart desktop app / reboot Windows | ❌ No change |

Existing Project Work Chats Still Function

One important observation is that previously created Project-backed Work chats continue to function normally.

For example, an older Work chat is still rooted in:

C:\Users\<username>\.codex\.chatgpt-projects\g-p-...

It can execute commands, access the mirrored project, and otherwise behaves normally.

The issue appears to affect only the creation of new Project-backed Work chats.

Desktop Log Evidence

The desktop logs consistently contain:

Could not sync ChatGPT project context

In one captured sequence, the application attempts to retrieve the Project and receives:

GET /gizmos/g-p-...

404
"This project can't be found. Check the link and try again."

Immediately afterward, the logs report:

Could not sync ChatGPT project context

followed by:

Could not use this project for a local chat

Additional Investigation

To further isolate the issue, I verified the following:

  • Existing Project-backed Work chats continue to function correctly.
  • Standalone (non-Project) Work chats can still be created successfully.
  • The problem reproduces across multiple existing Projects.
  • The problem also reproduces in newly created empty Projects.
  • Existing Project-backed Work chats remain rooted in:
C:\Users\<username>\.codex\.chatgpt-projects\g-p-...

This suggests the .chatgpt-projects mirror itself is healthy, since previously provisioned Work sessions continue to operate normally.

Summary

Based on testing, this does not appear to be a failure of Work mode itself because:

  • Standalone Work chats function correctly.
  • Existing Project-backed Work chats continue to function.
  • The failure occurs only when creating a new Work chat from a ChatGPT Project.
  • The failure occurs before the new Project-backed Work session is created.

From the observed behavior, it appears the failure occurs during the Project → Work context synchronization / provisioning stage rather than within the Work runtime itself.

If additional logs, diagnostics, or testing would be useful, I'm happy to provide them.

ftarari · 1 month ago

I can confirm that this issue is still present on Windows with desktop app version 26.721.4979.0.

It reproduces both with existing ChatGPT Projects and with a newly created empty Project. Existing Project-backed local chats continue to work, and standalone local Work tasks outside Projects can still be created.

Additional troubleshooting completed with no effect:

  • Windows Repair
  • Windows Reset
  • Sign out and sign back in
  • Full uninstall
  • Windows restart
  • Reinstall
  • Confirmed that Cloudflare WARP is disconnected
  • Confirmed that no Windows or WinHTTP proxy is configured

The desktop log still reports:

Could not sync ChatGPT project context

I submitted the affected session and diagnostic information through the desktop app.

Feedback/session ID: 019fa5fc-71b2-7040-aeb1-3cea9f46e3cb

ekdoestech · 1 month ago

Following for resolution.

LCL349349 · 1 month ago

Additional reproducible evidence from a Windows system, including a likely root cause and a concrete regression test.

Environment

  • Windows 24H2, build 26100.8875
  • Microsoft Store package: OpenAI.Codex 26.721.4979.0
  • Package status: OK
  • Multiple existing ChatGPT Projects are affected

Important reproduction pattern

  1. Fully restart Windows and open Codex.
  2. Creating a new local Work task inside an existing ChatGPT Project may succeed once immediately after restart.
  3. After that task is created and is running from the local project mirror, subsequent task creation fails with:
  • Could not sync ChatGPT project context
  • Could not use this project for a local chat
  1. The failure can then affect other existing ChatGPT Projects as well.
  2. Existing Project-backed tasks continue to work, and standalone local tasks outside ChatGPT Projects still work.

This is not a one-task-per-project limit. It is an unreliable project-context synchronization/provisioning flow: the first task may succeed, while later tasks fail.

Local investigation

Read-only inspection of the desktop application and controlled reproduction with disposable directories indicate this sequence:

  • Project synchronization prepares a replacement/staging mirror.
  • The implementation attempts to rename/replace the entire .codex/.chatgpt-projects/g-p-* project root.
  • An active Work task can use that same project root as its current working directory.
  • On Windows, renaming a directory that is being used as a process working directory fails with EBUSY / resource busy or locked.
  • The same failure was reproduced using a disposable directory with the same usage pattern.

Authentication, project retrieval, local filesystem permissions, disk space, and network access remained healthy. Restarting can temporarily remove the lock and explain why one task sometimes succeeds, but it is not a durable fix.

Suggested fix direction

Please keep the g-p-* root stable while tasks may use it as their working directory. Synchronize only the application-managed children (for example project instructions, sources, and metadata) using transactional child-level replacement, or move task working directories outside the mirror before root replacement. A retry alone may not be sufficient because the working-directory handle can remain live for the lifetime of the task.

Suggested Windows regression test:

  1. Create two consecutive local Work tasks inside the same existing ChatGPT Project while the first task remains active.
  2. Create a third task inside a second existing ChatGPT Project.
  3. Verify all tasks retain the correct ChatGPT Project context and local folder access.
  4. Verify the user does not need duplicate local projects, alternate project entries, app reset, or reinstall.

Please ship the fix through the signed Microsoft Store Windows package. A supported workaround that preserves the user's original single ChatGPT Project structure would also be valuable if the Store update will take time.

Recognition request

If this investigation and root-cause evidence materially help reproduce and fix the defect, I would appreciate consideration for additional Codex usage credits for the affected account. Extra usage capacity would help me continue detailed testing and provide high-quality feedback on future Windows releases. I understand that there may be no formal bounty or credit program, and this is a goodwill request rather than a condition of the report.

leichengyu23app-code · 1 month ago

Confirming this issue on another Windows configuration as of 2026-07-29.

Environment

  • Windows 10 22H2, build 19045
  • Microsoft Store package: OpenAI.Codex 26.721.4979.0
  • Multiple existing ChatGPT Projects are affected
  • Standalone local projects continue to work

Additional local evidence

After backing up and rebuilding the local ChatGPT Project mirror:

  1. Restarting the app and selecting a ChatGPT Project successfully recreated its mirror and metadata under %USERPROFILE%\.codex\.chatgpt-projects\g-p-*.
  2. Submitting the new local task shortly afterward failed again with Could not sync ChatGPT project context.
  3. The desktop log recorded the failed composer cwd as that same g-p-* mirror root.
  4. While the app was active, attempting to move the mirror root returned the Windows error that the path was in use by another process.
  5. The behavior reproduced across multiple unrelated ChatGPT Projects.
  6. Opening the same copied project context as an ordinary local project via codex://new?path=<local-folder> worked and produced a normal local project ID instead of a g-p-* ID.

This independently supports the directory-lock / root-replacement analysis in the previous comment: initial synchronization can succeed, but a later synchronization attempts to replace a project root that the active local task is already using. Keeping the g-p-* root stable and transactionally updating only its managed children appears to be the appropriate Windows-safe fix.

All paths above are sanitized; no project files or user data are included.

andrewcdobbins · 26 days ago

I can independently reproduce this issue in the Windows Codex desktop app.

Current status (1 August 2026):

  • Still reproducible after installing the latest Windows desktop update released today.
  • Starting a Work task from within an existing ChatGPT Project consistently fails with the project-context synchronisation error.
  • Creating the same Work task from the ChatGPT web application succeeds.
  • That web-created Work task then synchronises correctly and becomes visible in the Windows desktop app.
  • Regular Chat conversations inside Projects continue to work normally.
  • I have reproduced this across multiple Projects over several days, so it does not appear to be isolated project corruption.

From the observed behaviour, the Project context and subsequent synchronisation appear healthy; the failure seems specific to Windows desktop initialisation of Project → Work.

I am happy to provide the exact desktop build number or a feedback/diagnostic ID if useful.

fredtat-byte · 20 days ago

Hi guys, i was having the same issue and i can get it to work when i switch to the Ultra Model. It works like 75% of the time...it's like i have to go in a particular order of starting the work chat. But I do get it to work. Guess they want their token usage. lol

Hope this helps someone.

maddavo · 15 days ago

I can reproduce this reliably on Windows, and I have narrowed it down to a per-project failure rather than a general Work-mode failure.

Current environment:

  • Windows 10 Pro
  • ChatGPT Windows app / Codex integration
  • Current installed package: OpenAI.Codex_26.803.8161.0
  • ChatGPT Plus

Failing project

Existing cloud project: My PC & Network

A fresh cloud chat created directly inside this project correctly identifies the project, but attempting to start a local Work session fails with:

Failed to create chat

Could not use this project for a local chat

I reproduced this through multiple launch paths, including:

  • the in-chat Continue with Work handoff
  • the chat menu Continue in work mode

Both fail.

An existing genuine Project-bound Work session in the same project still works and reports a local project mirror under:

C:\Users\<username>\.codex\.chatgpt-projects\...

However, no new Project-bound Work session can currently be created for this project.

Control tests

Work mode itself works normally:

  1. A new projectless Work session can be created successfully.
  1. I created a completely new cloud project, Testing Project, created a fresh cloud chat inside it, and successfully started a genuine Project-bound local Work session.
  1. I then tested another long-established existing project, IoT Projects:
  • created a fresh cloud chat directly inside it;
  • started Work successfully;
  • the resulting Work session confirmed the correct project and a local mirror under C:\Users\<username>\.codex\.chatgpt-projects\....
  1. Immediately afterwards, without restarting the app or changing account/network state, I returned to My PC & Network and retried the same operation. It again failed with:

Failed to create chat

Could not use this project for a local chat

So this is a same-session A/B result:

  • IoT Projects → Work succeeds
  • My PC & Network → Work fails

Additional observation

Moving an already-created projectless Work chat into My PC & Network makes it appear under the project in the sidebar, but does not convert it into a genuine Project-bound Work session.

The Work agent still reports it as a projectless/generated workspace, whereas genuine Project Work sessions report a .codex\.chatgpt-projects\... mirror and project metadata.

This suggests the failure may involve per-project local mirror / synchronization / project metadata state, rather than Work mode, the account, networking, or all existing projects generally.

The behaviour has also been intermittent: this project has previously been able to create Work sessions, then later stopped doing so.

ajrobb · 6 days ago

Can confirm that this still is not working for the latest Windows Desktop App on a Pro subscription. Reverted to using web interface for now.