[FEATURE] Cowork live artifacts are desktop-only and machine-local — no way to view, sync, or create one from mobile

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Cowork live artifacts are, by documentation and by implementation, a desktop-only and machine-local feature:

• Help Center, Use Claude Cowork on web, desktop, and mobile: "Live artifacts are available on the desktop app only."
• Help Center, Use live artifacts in Claude Cowork: artifacts "reside on your computer and don't sync across devices."
• #63013 confirms they are plain files in a local folder (the path changed in 1.9255.2 with no migration).

A live artifact's whole premise is that it re-queries its connectors every time you open it. That premise is most valuable for artifacts you check repeatedly through the day, in short glances, wherever you happen to be: a prioritized "what needs attention now" list, a status board, a tracker. Those are exactly the artifacts you want on a phone — and today they are the ones you cannot have there.

Concretely, three things are missing:

1. The mobile Artifacts view does not list live artifacts at all.
2. There is no sync — artifacts are local files with no server-side copy.
3. There is no way to create, update, or refresh a live artifact from a mobile Cowork session.

I could not find an existing issue asking for mobile access to live artifacts, which is why I am filing this.

Proposed Solution

Any one of these would solve the problem. Listed cheapest-first, as far as I can judge from the outside.

1. Give the owner a per-artifact URL that renders in a signed-in browser on any device, even if the Artifacts list stays desktop-only. This looks like the smallest change: link-sharing for live artifacts already exists on Team and Enterprise, and #78792 shows a signed-in mobile browser renders a server-hosted artifact URL fine. The gap is that the mechanism points at other people in your org, never at you on your own second device.

2. A read-only mobile view. Sync the artifact HTML server-side and let mobile render it. Connector calls either execute server-side, or degrade to the last cached result with an explicit "last refreshed at" stamp, so staleness is visible rather than silent.

3. Failing both, an explicit "snapshot to cloud" on close or refresh, giving mobile a stale-but-clearly-labeled copy.

Option 1 alone would already move the feature from "only usable at the desk" to "usable away from it."

Alternative Solutions

Export a static HTML copy to cloud storage and open that in a mobile browser. It reads fine, but the connector refresh is gone — which is the entire point of a live artifact. What you get on mobile is a snapshot that silently ages, with nothing on screen saying how old it is.

Rebuild the same view as a scheduled task that pushes a text summary to chat or a messaging connector. This works, but it is a different product: a push digest you receive, not an artifact you can open and interrogate.

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

1. On the desktop app, I create a live artifact that reads a connector-backed database and renders a prioritized action list plus a few tracking views.
2. Through the day I want to glance at it repeatedly. Most of those glances happen when I am not at the machine that created it.
3. On the phone, the Artifacts view does not list it. There is no URL to open, and no way to ask a mobile Cowork session to refresh or rebuild it.
4. So I export a static copy to cloud storage and read that instead, knowing the numbers may be hours or days stale.
5. With any of the proposed options, step 4 disappears and the artifact stays current wherever I open it.

Additional Context

What I verified before filing (Max plan, desktop app + claude.ai web, same account)

• On claude.ai web, the Artifacts view's filter offers only All / Chat / Code — there is no Cowork category, and my existing Cowork live artifacts do not appear in the list or in its search. So live artifacts are absent from web too, not just mobile.
• On web, "New artifact" offers only chat-artifact categories (Apps and websites, Documents and templates, Games, …). There is no "Create Cowork artifact" entry point outside the desktop app.
• The release notes contain no entry about live artifacts reaching web or mobile, or syncing across devices.

This is not asking for something that already exists — but adjacent plumbing does

Three artifact classes already have a server-side representation:

1. Chat artifacts can be published publicly to a URL on Free/Pro/Max.
2. Claude Code artifacts get a claude.ai/code/artifact/<id> URL that renders on web and desktop.
3. Cowork live artifacts can already be shared by link — but only on Team and Enterprise, only inside the organization, and per the Help Center they "can't be published publicly on any plan."

So the machinery for serving an artifact from the server clearly exists, and it has already been pointed at live artifacts once. What is missing is narrower than "build sync from scratch": the owner of a live artifact has no way to open their own artifact from another device. Point 3 is aimed at other people; nothing is aimed at the same person on a different screen.

Related issues

• #78792 (open) — published Claude Code artifacts do not appear in the mobile Artifacts view. The reporter's browser-URL workaround suggests the blocker is discovery/listing rather than rendering.
• #63013, #51426, #57398, #55788 — all live-artifact issues, all desktop-scoped. No mobile counterpart exists.
• #65955, #58477, #81658 — adjacent cross-device sync gaps for sessions and conversations; same family of pain.

Environment

• Claude Desktop with Cowork; live artifact created from a Cowork session using a database connector.
• Mobile: Claude iOS app, same account.