ChatGPT Sites fails to scaffold — required @openai/sites@0.2.0 package returns “not found / no permission”
What version of the Codex App are you using (From “About Codex” dialog)?
26.818.31338
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
Bug report
Summary
ChatGPT Sites in Work mode is currently unable to create a new Sites project because the required scaffold package @openai/sites@0.2.0 cannot be accessed by the Work environment.
The failure occurs before any project files are created.
The Work session reports:
They require the exact scaffold package/version @openai/sites@0.2.0; that package returned “not found / no permission” in this environment before any project could be created. This is an access/provisioning blocker. Please retry once the Sites capability/package access has been enabled or restored, and I’ll resume from the required scaffold step.
Timing / regression
This appears to be a new regression on 21 August 2026.
Sites was working successfully for me earlier on the same day.
I successfully created/published two ChatGPT Sites on the morning of 21 August 2026.
Later that afternoon/evening, new Work sessions started failing at the scaffold stage.
The first failure I recorded was at approximately 18:29 BST on 21 August 2026.
There was no ChatGPT/Codex application update performed by me between the successful Sites deployments in the morning and the failures later in the day.
Steps to reproduce
- Open ChatGPT Work.
- Use the ChatGPT Sites capability/plugin.
- Ask Work to create a new Site.
- Work attempts to initialise the required Sites scaffold.
- The environment attempts to access the required package/version
@openai/sites@0.2.0. - Package access fails with “not found / no permission.”
- Work stops before creating the project.
Actual behaviour
No Sites project is created.
Work reports that the exact required scaffold package/version cannot be accessed and identifies the problem as an access/provisioning blocker.
Retrying in another new Work thread produces the same failure.
Expected behaviour
The Work/Sites environment should have access to the scaffold package required by the Sites capability and should initialise the Sites project normally.
Why this appears to be environment/provisioning related
The failure happens before project creation, so there is no project code involved that could be causing the failure.
The same account/environment successfully created and published two Sites earlier on 21 August.
The error specifically identifies access to the required Sites scaffold package as the blocker.
Environment
- Product: ChatGPT Work
- Capability: ChatGPT Sites
- Date: 21 August 2026
- Time first observed: approximately 18:29 BST
- Account: ChatGPT Plus
- Platform: ChatGPT desktop/web environment on Windows
- Sites had been working successfully earlier the same day
- No client update was installed between the successful and failing sessions
Error
Required package/version:
@openai/sites@0.2.0
Result:
not found / no permission
Work's diagnosis:
This is an access/provisioning blocker. Please retry once the Sites capability/package access has been enabled or restored.
Additional context
There have been recent Sites-related issues, but this particular failure appears to be a new issue occurring on 21 August.
Because Sites worked successfully earlier the same day and then stopped without a client-side update, this may represent a regression or provisioning/package-access change in the ChatGPT Work/Sites environment.
I can provide screenshots or additional Work-session details if required.
What steps can reproduce the bug?
Open ChatGPT Work.
Use the ChatGPT Sites capability/plugin.
Ask Work to create a new Site.
Work attempts to initialise the required Sites scaffold.
The environment attempts to access the required package/version @openai/sites@0.2.0.
Package access fails with “not found / no permission.”
Work stops before creating the project.
What is the expected behavior?
The Work/Sites environment should have access to the scaffold package required by the Sites capability and should initialise the Sites project normally.
Additional information
There have been recent Sites-related issues, but this particular failure appears to be a new issue occurring on 21 August.
Because Sites worked successfully earlier the same day and then stopped without a client-side update, this may represent a regression or provisioning/package-access change in the ChatGPT Work/Sites environment.
I can provide screenshots or additional Work-session details if required.
1 Comment
Additional reproduction: I have now also reproduced the same failure in a separate CoWork session. The required @openai/sites@0.2.0 scaffold package again fails with “not found / no permission”. This is therefore not isolated to the original Work thread/environment.