AGENT DESIGN · NO-BACKEND DASHBOARDS
Claude Code shipped a feature this week (v2.1.207–v2.1.212, July 13–17) where a published artifact can call MCP connectors every time someone opens it, through that viewer's own connections, not a copy of whatever the builder had access to. This is a small working demo of what that actually changes: not the UI, the trust model.
One published link, opened by three different people
Toggle the artifact model, then click each persona to simulate them opening the exact same shared URL.
buloy.space/lab/pr-dashboard · viewing as You (studio)
connector: github.com/vaestradaThis artifact wants to pull live data through You (studio)'s own GitHub connector. Nothing loads until this viewer approves it, once, on their own account.
Under the new model, the table above is not editable copy, it changes because a different account is asking. Same URL, 0 connector calls made so far, zero backend of my own holding anyone's token.
WHY THIS MATTERS FOR CLIENT WORK
The usual way to give a client a live dashboard is to stand up a backend, hold their API tokens somewhere, and maintain that surface forever. This flips it: the studio publishes one artifact, each client approves their own connector once, and the data that renders is always pulled live through their own account, never through mine. No token custody, no server to keep patched, and the same link genuinely means something different depending on who opens it. The tradeoff is real too: it only works for people who already have the right connector configured on their own account, so it is not yet a drop-in replacement for a proper client portal.
Built 22 July 2026 · pattern sourced from Claude Code's Week 29 digest