It is a small, specific disappointment. You spent an hour with your AI shaping a dashboard, a proposal, or a little interactive tool until it was exactly right. You shared the link. It landed well. And then, a week later, someone clicks it back to you: "this doesn't open anymore."
AI tools are very good at making things now. They are much weaker at the boring part that comes after: giving the thing a real address that survives contact with the real world. This guide explains the three reasons AI links vanish, what a permanent link actually needs to be, and how to get one in a single sentence.
The three reasons AI links disappear
When a shared link breaks, it is almost always one of these. They look the same to the person clicking, but the fix is different for each.
| What happened | Why the link died |
|---|---|
| It was a temporary preview | Many quick-share and demo hosts expire pages automatically after a fixed window. Great for a throwaway. Fatal for anything anyone bookmarks. |
| You edited it | With snapshot-style publishing, every publish mints a new URL. The version your recipient saved is now the stale one, and you are back to "use this link instead." |
| You never owned the address | The page lived on a domain the tool controls. If the tool changes, prices you out, or shuts the feature down, the link goes with it. You were renting. |
The first two are about permanence. The third is about ownership. A link that lasts has to solve both, and most tools that produce AI artifacts solve neither, because hosting and sharing were never the point of the product.
What a permanent link actually needs to be
"Permanent" is doing a lot of work in that sentence. In practice, a link you can safely put on a proposal or send to a client needs four properties at once.
1. A stable address that survives edits
The URL should not change when the content does. You refine the artifact next week, and the same link quietly shows the new version. No re-sending, no "final v3," no hoping nobody opens the old one in a meeting.
2. It does not expire on a timer
The page stays up until you decide otherwise, not until a countdown you never saw runs out. If you want expiry, it should be a choice you make, not a default you inherit.
3. You decide who can open it
Permanent should not mean public. A real sharing layer lets you keep a link private by default and choose per link: specific people, anyone with the link, password-gated, or fully open. "Anyone on the internet who guesses the URL" is not a sharing model.
4. You can take it with you
Ownership is not real if you cannot leave. The content should be exportable as open HTML whenever you want, so a permanent link is a convenience, never a trap. This is the difference between a home and a rental.
How to get one, from inside the conversation
The fix is not to abandon your AI and go learn about web hosting. It is to give your AI somewhere real to publish. Bauta connects to Claude, Claude Code, Cowork, ChatGPT, and Codex as a connector over MCP, the open protocol. After a one-time setup, publishing is a single sentence:
Behind that sentence, the four properties above are handled for you:
- The URL is permanent and stable. Edit the artifact tomorrow or next quarter, from the same chat or a new one, and it republishes to the same address. Previous versions stay in history.
- It does not expire. The page is yours until you change or delete it. Timed expiry is available if you want it, never imposed if you do not.
- It is gated by default. Every link starts private. You choose who can open it, with optional password protection and view analytics.
- It is portable. Content is stored as open HTML and you can export it at any time. A permanent link that you cannot leave is just a nicer cage.
There is a quieter benefit too. Because the page lives at a stable URL as structured HTML rather than a frozen file, other people's AI tools can read it as well. A link that both humans and agents can open is worth more than an attachment in an inbox, which is the whole argument in why a live link beats a PDF for AI-made documents.
When a disposable link is still the right call
Honesty beats a pitch. If you are showing a friend a toy, demoing something internally that nobody will revisit, or posting a one-off experiment, a temporary or built-in share is the fastest path and you should use it. Permanence is worth setting up the moment the thing you made becomes part of your work: a deliverable, a recurring report, anything with your name on it. That is the line. Everything above it deserves a real address.
Frequently asked questions
Why did my shared AI link stop working?
How do I get a permanent link for something my AI built?
Does editing my artifact break the link?
Can I move my page if I stop using the tool?
Give your next artifact an address that lasts
Connect Bauta to your AI once, then say "share this." Free plan, permanent links, no credit card.
Try it now →