Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- First identify the entry point and action that produced the error.
- Inspect memory mode and role permissions, comparing one condition at a time.
- Troubleshoot shared direct-link access separately; the earlier incident has been resolved.
Distinguish opening a project from starting a local task
The notice that a project cannot be used for local chats cannot, by its wording alone, be mapped to one definite cause. Current official help explains project-memory and Work-permission restrictions, but does not identify this Chinese notice as a diagnosis of a single failure. First record the entry point clicked, the complete notice, and the last step before it appeared.
With the same account and workspace, first make a read-only check that the original project opens in ChatGPT on the web. If the web project works but selecting it and creating a local Work chat on desktop fails, inspect the usage conditions in the next two sections. If the original shared URL also fails on the web, follow the direct-link branch. Similar references to a “project” do not establish that local creation failure is a recurrence of the old incident.
Inspect project memory without changing the context boundary first
Official guidance states that projects using Project-only memory cannot use ChatGPT Work. Shared projects always use this mode and cannot switch back to Default memory. Inspect the setting at Project → ••• → Project settings → Memory. The restriction concerns Work; it does not mean that all ordinary Chat or mobile access within shared projects is unavailable.
Memory mode controls the context boundary between the project and outside conversations. This check only reads the current value; it does not require switching modes to start a task. Do not delete the project, stop sharing it, or remove members as troubleshooting experiments. Team materials and access relationships should not be used as test variables.
Record the memory mode, whether the project is shared, and the selected entry point together. If the usage conditions are not met, first decide whether ordinary Chat within the project can complete the task. If Work is needed, plan a workflow that satisfies permissions and material scope separately instead of repeatedly clicking the failing entry point.
Web Work availability does not establish desktop local permissions
On desktop, select ChatGPT at the upper left, then switch between Chat and Work. Official guidance controls Work Cloud, Work Local, and Codex Local separately. Administrators can inspect roles at Workspace settings → Permissions & roles. Ordinary Chat remains available under these settings.
The official FAQ says cloud and local Work permissions may update at different times. If web access works but desktop local access does not, first ask the administrator to confirm the Work permissions assigned to the role. If already enabled, local permissions may still need time to catch up before contacting support.
In a handoff, specify the account, workspace, and role, and identify which entry point fails. A colleague being able to start a task does not prove your client is broken: the two users may have different roles or be opening different projects.
Narrow the cause with a minimal comparison
Keep the same account and workspace while comparing web project access with desktop local Work creation. Success in the former and failure in the latter only establishes that the two entry points behave differently. It narrows the investigation but does not directly prove which switch or client issue is responsible.
If further comparison is needed, run a simple task without files in an authorized environment that already permits Work and record whether it starts. Change either the project or the entry point, not both, and avoid simultaneously switching accounts, changing memory, reinviting members, and changing networks. A successful comparison does not automatically make the original shared project supported.
Describe results as a specific action and observation, such as “The original account can open project chats, but a notice appears after selecting Work.” This helps administrators diagnose more than “all of ChatGPT is unusable” and reduces unrelated permission changes.
If a shared direct link does not open, check access eligibility
Ask the owner to open Share and inspect members and the sharing method. The person opening the link should check their account and workspace. Current documentation says invitations in managed workspaces may be restricted by workspace settings. Do not apply personal-account link behavior directly to enterprise workspaces.
If the project already appears in the sidebar, open it once from there using the same account and compare with the original direct link. Only the direct link failing, both entry points failing, and opening successfully but being unable to start Work are three separate outcomes to record. The sidebar is not a guaranteed fix.
Do not broaden access to anyone with the link merely to test it, and do not repeatedly remove and reinvite members. Use a controlled channel to hand off links. State whether the account has joined, which entry point failed, and the notice shown. Do not paste complete shared links into public support posts.
The old direct-link incident is resolved; retain it as historical context
OpenAI recorded an incident affecting shared-project direct links on September 10, 2026, and announced full recovery of affected services at 14:28 UTC that day (22:28 Beijing time). That was a completed incident. It does not establish that a present error with similar wording is the same incident.
If failure remains after checking current conditions and permissions, provide an administrator or official support with the client version, occurrence time, entry point, memory mode, role-check findings, and comparison observations. Share only information needed for diagnosis; there is no need to upload the entire project.
Investigate connectivity separately only when actual network symptoms such as DNS, TLS, proxy authentication, or connection timeouts occur. Project capabilities and role permissions do not automatically change with the IP address. Do not substitute a new public link, project deletion, or a broader memory scope for establishing the cause.
Sources
Frequently Asked Questions
What should I check first if Work works on the web but not locally on desktop?
Check the same account's workspace role and local Work permissions first. Official guidance says cloud and local permissions may not update together.
Should I delete the project or stop sharing it after seeing this notice?
Do not use those actions as trial-and-error fixes. Read the settings first, distinguish project access from task startup, and hand off the specific failing action.