Live Artefacts: Claude as Your Personal Dashboard
Claude artefacts can reach out to live data sources and pull in real content every time you load them. This opens up new possibilities.
I've been building dashboards at work recently that I'd normally have had to justify as a proper engineering project. One pulls together Pendo and Langfuse data into a single view - product usage alongside AI service metrics in a way neither tool surfaces natively. It took an afternoon.
Most artefacts in Claude are snapshots. You ask for something, it generates it, and that's what you've got. Useful, but static. A Live Artefact reaches out to a real data source every time it loads, pulling current information through an authenticated connection rather than rendering something Claude baked in earlier.
What makes them different
The shift is subtle on the surface but I think it's significant in practice. A regular artefact showing your content calendar is a one-time render. A Live Artefact showing your content calendar is actually reading from your CMS right now.
That turns the artefact from a generated output into something closer to an interface. You're not looking at a thing Claude made. You're looking at your data, shaped the way you asked for it.
What you can actually build
On the personal side, I built a content calendar for cmdzed.com that shows scheduled and published posts in a proper calendar layout. Every time I open it I can see what's coming up and spot gaps without logging into Ghost and piecing the picture together manually. Small thing, genuinely useful.
The common thread in what I've built is data from different places, presented exactly how I want it, without building an actual application. In my experience that covers a lot of ground - reporting views, cross-tool dashboards, anything where you want a persistent window into your own data.
Claude as a dashboarding layer
MCP has become a fairly broad protocol at this point. Most tools people use for work have some kind of MCP integration, which means Claude can reach them. Live Artefacts let you do something useful with that connectivity - not just ask questions about your data, but build views over it that keep working.
It puts Claude somewhere between a chat tool and a lightweight app builder, I think. Worth experimenting with if you haven't already.
The current limitations
A few things worth knowing. Live Artefacts are Cowork-only right now, which means desktop. No mobile, at least at the time of writing.
They're also non-shareable currently. Whatever you build lives on your machine, for your use. That's a real constraint if you were hoping to build team views or share reporting with colleagues - but it also means the authenticated data stays entirely with you, which is probably the right call at this stage.
