July 14, 2026 · 5 min read
Claude Cowork can now pin a Live Artifact that refreshes with your data every time you open it. A designer on our team asked if it changes how we share HTML. I tried it. Here is the honest split: Live Artifacts are for fresh data inside Claude, ShareMyPage is for sending a page to anyone, anywhere.
A designer on our team dropped a link in Slack this week with a note: "worth a read, might change how we use and share HTML files." The link was Claude's new Live Artifacts in Cowork. His point was fair. Claude's HTML files aren't static anymore. You can pin one as a "Live Artifact" and it refreshes with current data every time you open it.
I'd already tried it. It's genuinely good, and it's also solving a different problem than the one ShareMyPage solves. So instead of the "which one wins" answer nobody actually needs, here's the honest split: what each is built for, and when I reach for which.
What a Live Artifact is genuinely good at #
A Live Artifact is a persistent HTML page Claude builds for you inside Cowork. The thing that makes it "live" is that it re-queries your connected apps when you open it. Ask for a dashboard of open tasks across Linear and Asana, or a morning brief with your Slack mentions and today's calendar, and it shows today's state, not the day it was built. Every iteration is saved as a version you can compare and restore.
That's a real capability, and it's the part ShareMyPage does not do. A shared page on ShareMyPage is a snapshot: it renders exactly what you published. If the underlying data changes, you republish (or have Claude re-push it over MCP). For a private dashboard you keep coming back to, a Live Artifact that quietly refreshes itself is the better tool. I'm not going to pretend otherwise.
Where Live Artifacts stop #
The catch is in three words: they don't leave. They don't leave Claude, they don't leave your organization, and they don't leave your machine.
They don't leave Claude. A Live Artifact opens in the Claude Desktop app. To view one, the person on the other end needs Claude Desktop installed and needs to be in your Claude organization. There are no public or external links, and no picking specific recipients. Anyone in your org with the link can open it, and nobody outside it can.They don't leave your org. Sharing is Team and Enterprise only, and it stays inside the organization. A client, a contractor, or someone in another company is out of scope by design.They don't leave your machine. Live Artifacts live on your computer. Switch devices and they don't come with you. They're desktop-only too, so there's nothing to open on the web or on a phone.
There's one more thing worth knowing before you lean on them: a Live Artifact uses your approved connectors without asking each time. That's the tradeoff that makes the refresh feel seamless, but it means a page that can change your data will do so on open. Worth a second thought before you pin one that writes, not just reads.
None of this is a knock. It's the shape of a tool built to keep a private view fresh for you and your team, inside Claude. It's just a different shape from "send this to someone."
What ShareMyPage is for #
ShareMyPage starts where Live Artifacts stop. You take an HTML or Markdown page, from Claude, from any other tool, or written by hand, and it becomes a real URL that opens in any browser, on any device, with no account and no app to install. The person you send it to just clicks a link.
The other half is who gets in. You decide per page: fully public, behind a password, or limited to your workspace. A ShareMyPage link can go to a client, a candidate, an investor, or the whole internet, none of whom will ever touch a connector of yours, because the page is a snapshot served in isolation. (If you want the details on how we run that untrusted HTML safely, I wrote up the sandbox model here.) You still get version history, so a snapshot isn't a dead end.
Side by side #
| Live Artifacts (Cowork) | ShareMyPage | |
|---|---|---|
| Content | Live, re-queries your apps on open | Published snapshot, versioned |
| Opens in | Claude Desktop app | Any browser, any device |
| Viewer needs | Claude Desktop, in your org | Just the link |
| Who can view | Your Claude org only | Public, password, or workspace |
| External sharing | No | Yes, anyone you grant |
| Where it lives | Your computer, doesn't sync | Cloud, on a real URL |
| Access model | Viewer's own connectors | Author controls entry |
They're closer to a pair than a fight #
The neat part is that these two fit together. Claude can generate a page and, over our MCP integration, push it straight to ShareMyPage as a link. So the same Claude that keeps a Live Artifact fresh for you internally can hand you a public, access-controlled version to send outward. One for the view you live in, one for the view you ship.
The short version #
Need a dashboard that refreshes itself while you work inside Claude? Pin a Live Artifact. Need to put a page in front of someone who isn't in your Claude org, on whatever device they happen to be holding, with you deciding who gets in? That's the job ShareMyPage was built for, and the one Live Artifacts deliberately leave alone.
Have a page to send to someone? Create it on ShareMyPage and paste your HTML in.