You open chatgpt.com/share/abc-123, see a full conversation, but you can’t reply and it never shows up in your sidebar. A lot of people read this as “I’m logged into someone else’s account.” You’re not. A shared link is a public, read-only snapshot of the conversation as it looked the moment it was shared. Anyone with the URL can read it, and it grants zero access to the sharer’s account, files, or history.
Fastest answer: If you just want to keep working from what you see, type a reply. ChatGPT silently saves a private copy into your account and you continue from there. The sharer never sees that copy. If you only want to view it, do nothing — there’s nothing to log into.
One thing changed in the UI: the old “Continue this chat” button that used to sit in the top-right of a shared page has been deprecated for all plans (as of June 2026). The fork-into-a-copy behavior is still there — it now triggers when you send a message, rather than from a dedicated button. If you’re hunting for that button, that’s why you can’t find it.
Which bucket are you in?
| What you see | What’s actually happening | What to do |
|---|---|---|
| Full chat, no input box, “Log in / Sign up” top-right | You opened the link logged out | Read it as-is, or log in to save a copy |
| Full chat, your avatar top-right, but it’s not in your sidebar | You’re a viewer; viewing doesn’t add anything to your account | Send a message to fork a private copy |
| You sent a message and a new chat appeared in your sidebar | You forked a private copy | Keep working; the sharer can’t see it |
| Tried to open a file / custom GPT the sharer used and got “no access” | The link only carries text, not the sharer’s assets | Recreate the asset in your own account |
chatgpt.com/share/... link 404s or says “not found” | Sharer deleted the link or the source chat | Ask them to re-share |
Common causes
1. A shared link is a snapshot frozen at share time
URL pattern: chatgpt.com/share/<uuid>. It’s a static copy of the conversation as of when the sharer clicked Create link. Messages either side sends after that point are not included — OpenAI even warns at share time that “messages sent or received after sharing your link won’t be shared.”
How to tell: the URL contains /share/, and the page renders read-only with no normal composer at the bottom.
Exception: on ChatGPT Enterprise, a shared chat does keep showing new messages added to the source conversation after sharing. The freeze-at-share-time rule below is for Free / Go / Plus / Pro / Team links.
2. You opened it logged out, so there’s no composer
Open a shared link without being signed in and the page shows the conversation plus a “Sign up to chat” prompt. That’s not access-denied — shared links are publicly readable. You only need an account to save your own copy.
How to tell: top-right shows “Log in” / “Sign up” instead of your avatar.
3. The shared chat isn’t in your sidebar
You’re looking at someone else’s snapshot. As a logged-out visitor you have no chats at all. Logged in, your sidebar only ever lists your own conversations — a shared link you merely viewed is never added.
How to tell: your email/avatar shows top-right (you’re logged in), but the conversation is absent from the sidebar.
4. Thinking the sharer sees your replies after you fork
When you send a message on a shared page, ChatGPT copies the snapshot into a brand-new conversation in your account and continues from there. From that point the chat is private to you. The sharer cannot see anything you write, and your copy survives even if they later delete the original link.
How to tell: after you reply, a new conversation appears in your sidebar containing the original messages plus your new one.
5. Thinking the link carries the sharer’s files / memory / GPTs
It doesn’t. The link contains only the conversation text. Specifically:
- Attachments (files, images) render in the read-only view but can’t be downloaded or re-used in your fork.
- Custom GPTs / tools: if the original chat called a custom GPT, your copy invokes the version available in your account — possibly a different or missing one.
- Memory: the sharer’s saved memory entries do not transfer. Your fork runs against your own memory.
How to tell: after forking, try to re-run a tool or open a file the sharer used — you’ll get “no access” or it falls back to your own version.
How to use it correctly
It’s not a bug, it’s the design. Here’s the right path for each goal.
Goal A: You got a shared link and want to keep working from it
Open the link → read the conversation (read-only)
→ Want to continue? Type a message in the prompt area and send
→ ChatGPT logs you in if needed, then copies the chat into your account
→ A new conversation appears in your sidebar; you continue from thereAfter you fork:
- The content is a snapshot copy of what was shared, up to the share moment.
- Everything you write afterward is private; the sharer can’t see it.
- The model and any GPTs/tools used are yours, not the sharer’s.
If there’s no prompt area at all and nothing happens when you try to type, the link is view-only by design — you can still copy the text out manually.
Goal B: You want to share one of your own chats
Open the chat → click Share (top-right of the conversation,
or the ••• menu next to the chat in the sidebar)
→ In the modal, click "Create link"
→ Optional: include your name (default is anonymous)
→ Optional: toggle whether the link is discoverable by search engines
→ Click "Copy link" → send itThings to know:
- New messages you add to the chat do not auto-update the shared version. To publish later messages, open Share again and create a fresh link.
- The modal warns: “anyone with the URL will be able to view your shared chat.” Treat the link as public.
- Once someone has forked your shared chat into their account, their copy survives even after you delete your link.
Goal C: Real collaboration (multiple people editing one chat)
Public links can’t do this — they’re one-directional snapshots. Use a workspace instead.
| Type | Available on | Who can view | Two-way collaboration |
|---|---|---|---|
| Public share link | All plans | Anyone with the URL | No — viewers can only fork a private copy |
| Workspace shared chat | Team / Enterprise | Workspace members | Yes — members can keep writing in the same chat |
| Project sharing | Plus / Team / Enterprise | Project members | Yes, within the shared project |
For people to write into the same conversation, you need a Team or Enterprise workspace, not a public link.
Goal D: Don’t leak sensitive data through a public link
A shared link is a public URL, with the same risks as posting a page on the open web:
- If you make the link discoverable, search engines can index it. ChatGPT’s discoverable shared chats were found in Google’s index in mid-2025, after which OpenAI rolled back default discoverability. Leave the discoverability toggle off unless you mean it.
- Once you’ve sent the URL to someone, you can’t un-send it; revoking only stops new viewers.
- Never share chats containing API keys, passwords, government IDs, customer data, or proprietary code.
Goal E: Find and revoke links you’ve already shared
Click your avatar (bottom-left) → Settings → Data Controls
→ Shared Links → "Manage"
→ The modal lists every chat you've shared (title + share date)
→ Trash icon = delete/invalidate that linkOr revoke a single link from the chat itself: open Share → delete icon → “Delete link”. Deleting the source conversation (sidebar ••• → Delete) also invalidates its shared link.
Note: as covered above, deleting a link does not remove copies that viewers already forked into their own accounts.
How to confirm it’s fixed
- As a viewer who wanted to continue: send one message; a new conversation with the original transcript plus your message should appear in your sidebar. That’s your private copy.
- As a sharer who revoked a link: open the
chatgpt.com/share/...URL in a private/incognito window — it should now return a “not found” page rather than the conversation. - Checking what’s still public: Settings → Data Controls → Shared Links → Manage should match what you intend to have shared; delete anything stale.
Prevention
- For team collaboration, use Team/Enterprise workspace shared chats, not public links — public links can’t support multi-user editing.
- Never publicly share chats with sensitive data, and keep the discoverable toggle off so links stay out of search results.
- Back up important chats with Export (Settings → Data Controls → Export data) — shared links can be deleted and disappear.
- Periodically prune Settings → Data Controls → Shared Links → Manage to shrink your historical exposure.
- If you work on a team, write a one-paragraph “shared link vs workspace chat” note so newcomers don’t treat public links as collaboration.
FAQ
Why can’t I reply on a shared link the way I would in my own chat? Because the page is a read-only snapshot, not a live session. When you do send a message, ChatGPT forks a private copy into your account and you continue there — it never writes back to the sharer’s chat.
Where did the “Continue this chat” button go? It was deprecated for all plans (as of June 2026). The same fork-to-a-copy behavior now happens automatically when you send a message on a shared page, so there’s no separate button.
Can the person who shared the link see what I typed afterward? No. Your fork is a separate, private conversation in your own account. The sharer has no visibility into it, and it persists even if they delete their link.
If I delete the shared link, does the other person lose their copy? No. Deleting the link only stops new people from opening it. Anyone who already forked the conversation keeps their independent copy.
Could my shared chat end up on Google? Only if you turn on the discoverability option. After public ChatGPT chats showed up in search results in mid-2025, OpenAI made non-discoverable the default. Anyone with the raw URL can still view it, so don’t share secrets.
Does the shared link include the files or custom GPT from the original chat? No. It carries only the conversation text. Attachments display but aren’t downloadable in your fork, and any custom GPT falls back to the version in your own account.
Related reading
- Shared link not opening
- History missing
- Account switch not working
- Team seat not active
- Mobile and web login mismatch
Tags: #ChatGPT #ChatGPT account #Troubleshooting #Debug #Shared link