You rename a ChatGPT Project from Q3 Sales Research to Q3-Q4 Sales Research, click the old share link from your handover doc, and get a 404 — or worse, the link still works but lands on an old read-only snapshot that does not include the new files. Project share links sometimes include the project name as a slug, and the slug is regenerated on rename. Old links may stop resolving, and even when they do they can point at a stale version. The fix is to treat renames as breaking changes: regenerate the share link, re-test in incognito, then update every place you posted the old URL.
Common causes
1. Share link contains the project slug, not just an ID
Some Project share URLs look like chat.openai.com/g/project-<id>/q3-sales-research. When you rename, the trailing slug changes and old slugs can stop resolving. Even if the platform redirects, it may not on every region or client.
How to spot it: Old URL ends in a slug that matches the old project name. New URL ends in the new slug.
2. Link was generated against a snapshot, not the live project
Some sharing modes (especially anonymous read-only shares) freeze the project at the moment of share. Renaming the live project doesn’t update the snapshot — but the snapshot also doesn’t see new files added after the share was made.
How to spot it: Old share link still opens but content is missing the latest uploads.
3. Browser / proxy cache returns the old slug from history
If you bookmarked the URL or your browser autocompletes from history, you may keep hitting the old link even after a rename, get the cached 404, and assume the project is broken.
How to spot it: Same URL works in incognito but fails in your normal window — pure cache issue.
4. Sharing was disabled then re-enabled
Toggling Share off and back on rotates the link token. Anyone with the old link gets a permission error even though the project is live.
How to spot it: Link returns a “you don’t have access” message rather than a 404.
5. Project was moved between workspaces (Team / Enterprise)
Moving a project from personal to Team workspace changes the URL root entirely and old personal links cannot resolve to a Team-scoped resource.
Shortest path to fix
Step 1: Test the old link in incognito before assuming it’s broken
Open a private window, paste the old URL. If it loads, your normal browser had a cached redirect or a stale tab — fix the cache, not the link. If it 404s in incognito too, the link is genuinely broken.
Step 2: Regenerate the share link after every rename
In the Project, open the share menu, click Revoke link (or disable sharing), then re-enable. Copy the fresh URL. Test it once in incognito.
Old: chat.openai.com/g/project-abc123/q3-sales
New: chat.openai.com/g/project-abc123/q3-q4-salesThe new URL has the current slug. Use this everywhere.
Step 3: Pick stable names you do not plan to rename
Avoid embedding dates or scopes you may need to extend (Q3 becoming Q3-Q4). Use scopeless names like Sales Research 2026 or Customer Onboarding Project. Renames are rare when the name doesn’t encode time-bound scope.
Step 4: Update every place the old URL was posted
Search Slack, Notion, email, your handover doc. Replace old links with the new one. If your team treats Project URLs as long-lived references, post the new link in the same thread so the change is auditable.
Step 5: Verify the new link in a fresh account
Have a teammate (or a second account) open the new URL. Confirm they can read the project and see the latest files. This rules out account-specific permission caching.
Prevention
- Treat Project renames as breaking changes — schedule them, communicate them, and regenerate the share link as part of the same operation.
- Before sharing a Project URL, test it in incognito so you know it works without your session.
- For long-lived references (handover docs, runbooks), do not paste raw share URLs. Paste the Project name and a short instruction like
search Projects for "Q3 Sales Research"so the reader resolves the link themselves and always gets the live version. - If you maintain many Projects, keep a central index doc with
name - owner - current share URL - last verified date. Update it whenever you rename. - For mission-critical handoffs, prefer Team workspace shares over personal-account links — workspace URLs survive ownership changes.
Prevention checklist for renames
- Note the old name and link in your change log.
- Rename the Project.
- Revoke and regenerate the share link.
- Test new link in incognito.
- Update all posted references.
- Notify anyone who had the old link.
How to confirm the fix
After regenerating, run this verification triple:
- Open the new URL in your normal browser - it loads.
- Open the new URL in incognito - it still loads (no session-dependent quirks).
- A second account or teammate opens it - they can read it.
All three pass: the new link is safe to publish. If the second or third check fails, sharing permission scope didn’t apply globally — open share settings again, confirm the audience (anyone with the link vs workspace members only) matches your intent.
If still broken
- Make sure the Project itself isn’t archived. Archived Projects sometimes return their public link as 404 even when the workspace owner can still see them.
- Confirm your workspace tier. Some Enterprise tenants disable external share entirely — the link only works for tenant members.
- If you renamed and now the Project doesn’t show up in your sidebar at all, search by old name once: Projects are sometimes filtered by recent activity and a rename pushes them out of the default view.
- Last resort: duplicate the Project under the new name, copy files / instructions, retire the old one. Share the new Project URL going forward.
If still broken after regenerating
Edge cases worth checking:
- Confirm the Project actually has share enabled. After revoke, it sometimes stays disabled until you flip it back on.
- Make sure you’re sharing the Project itself, not an individual chat inside it. Chat shares and Project shares are different URLs with different lifetimes.
- File a ticket at help.openai.com with the old URL, new URL, and a screenshot showing both — share-URL bugs are tracked separately from general Project bugs.
Common pitfalls
- Renaming the Project on mobile vs desktop sometimes generates slightly different slugs — always confirm the live URL from the same client your users will use.
- A regenerated link is not retroactive: people who saved the old URL still have the broken one. Push the new URL through the same channel you originally shared it.
- Custom GPTs (different feature from Projects) follow a similar pattern — renaming a GPT can break its published URL slug too.