The argument in one line.
Live artifacts in Claude Cowork let you build persistent, connector-backed dashboards that refresh with fresh data on demand without re-prompting, eliminating the need to manually update static snapshots across seven high-leverage business workflows.
Read if. Skip if.
- A solo online business owner who uses Claude regularly and is tired of rebuilding the same dashboards every week by re-prompting from scratch.
- A community builder, course creator, or membership operator who wants a live artifact that surfaces what members are actually asking for, without manually reading hundreds of form responses.
- A content creator managing inbound sponsorship and collaboration emails who wants a single dashboard that scores and prioritizes opportunities by fit and revenue potential.
- A product launcher who currently juggles Stripe, Gmail, and ad dashboards in separate tabs during a live launch and wants one consolidated live view.
- You are on a free Claude plan — live artifacts in Cowork require a paid subscription of at least $20 a month and are not available otherwise.
- You need dashboards that sync across multiple devices or that team members can share; at time of recording, live artifacts are local-only with no sharing or cross-device sync.
- You are a developer or data analyst already building custom dashboards — this is a no-code business-owner workflow that will feel limited if you can build proper data pipelines.
The full version, fast.
Claude's new live artifacts inside Cowork turn the usual static dashboard into a persistent sidebar page that pulls fresh data from your connected tools every time you click refresh, so you stop re-prompting and stop burning tokens to rebuild the same view. The mechanism is simple: enable connectors like Gmail, Google Calendar, Slack, Notion, Stripe, or vidIQ through MCP, then prompt Claude once with a detailed spec covering visual style, data sources, layout sections, and the specific metrics or filters you want, and Claude builds an interactive page that lives across sessions. Use this pattern to compress scattered tools into single-purpose dashboards for daily operations, content analytics, community signal, competitor tracking, launches, inbound deal triage, and personal review.
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.

01 · Cold open + promise
Names the problem (static artifacts) and the new thing (live artifacts). Promises 'what they are, how to set up, seven use cases.'

02 · What live artifacts actually are
Side-by-side Regular vs Live comparison card. Three reasons they matter: persistence, interactivity, fresh data.

03 · Four caveats up front
Local-only storage, no sharing yet, paid plans only ($20+/mo), no context-window indicator so it silently compacts.

04 · Where to find them + connector setup
Cowork → Live artifacts → New artifact. Walk through Anthropic-native connectors (Gmail, Calendar, Slack, Notion) and permission scopes (read-only / write / always-allow).

05 · Custom + Zapier MCP fallback
If an app isn't in the directory: paste an MCP server URL as a custom connector, or use Zapier MCP (8,000+ apps). Five-minute setup.

06 · Use Case 1: Daily Command Center
One page with calendar, unopened emails, Slack mentions, revenue, tasks, plus a weekly-pulse section (MRR, signups, churn, Q2 projection, refunds). About 10 minutes to set up.

07 · Use Case 1: The prompt walkthrough
Shows the actual prompt — 'looks and feels like Stripe, Linear, or Vercel,' design principles, layout structure. Notes Live Artifacts default to Haiku 4.5 and you can't change the model. Compaction kicks in mid-build.

08 · Use Case 2: YouTube Growth Tracker
Subscribers, goal progress, 90-day forecast, top performers (last 7 days), and the 'format pulling weight' tile that compares shorts vs long-form. Powered by vidIQ MCP.

09 · Use Case 3: Community Member Question Radar
His favorite. Scans new-member intake Google Sheet weekly. Returns AI-level distribution, discovery channels, top 5 feedback themes with mention counts, plus content recommendations for newsletter / YouTube / school posts. Compounds with growth.
10 · Mid-roll: Zone of Genius app
Soft CTA tucked right after the high-engagement use case. Pitches the AI Playbook membership + Zone of Genius app (pre-built AI workflows trained on Rick's IP).
11 · Use Case 4: Competitor Watch
No native connector needed — Claude uses web search to track 3 competitors for uploads, blog posts, pricing changes, social posts. Adds vidIQ MCP for YouTube. Outputs competitor cards + 5 content ideas based on competitor activity.
12 · Use Case 5: Launch Dashboard
For live product launches — pulls from Stripe / Gmail / Bitly / Slack / affiliate platform. Units sold, total revenue, pace-to-goal, daily sales momentum, refund rate. Demoed with CSV uploads since not currently launching.
13 · Use Case 6: Sponsor & Collab Triage
Points at his collaborations-only Gmail inbox. Classifies inbound sponsor/affiliate emails as good-fit / maybe / not. Surfaces ~$14K of opportunity. Fit criteria baked into the prompt.
14 · Use Case 7: Journal + Goals + Habit Tracker
Saved for last as 'most surprising.' Three tabs — today's reflection (energy/mood sliders, what worked, tomorrow's focus), goals progress, and pattern analysis (30-day energy/mood trends, habit streaks, monthly key-action recommendation). Cross-references journal entries with Google Calendar.
15 · Close + final CTA
Restates the unlock: build once, lives in sidebar, updates on demand. End-roll pitch for AI Playbook + Zone of Genius app.
Lines worth screenshotting.
- Live artifacts inside Claude Cowork are persistent dashboards that pull fresh data from connected tools on click — no re-prompting, no stale snapshots.
- A daily command center dashboard can replace five browser tabs by pulling calendar, email, Slack, revenue, and task data into a single refreshable page.
- Live artifacts live locally on the machine they were built on and do not sync across devices yet — this is a current limitation, not a permanent design.
- The weekly pulse view inside a live artifact gives a Monday morning business health check without opening any analytics tool separately.
- Connectors (MCPs) are the data layer under live artifacts — adding Notion, Gmail, Google Calendar, or Slack takes about five minutes of authorization.
- Zapier MCP connects live artifacts to over 8,000 apps that do not have a native Anthropic connector, making the data layer nearly universal.
- A competitor watch dashboard built as a live artifact lets you refresh and see changes in competitor positioning without a dedicated monitoring tool.
- A sponsor and collaboration triage artifact converts an inbox-scanning task into a single-click overview sorted by priority and deadline.
- A journal-plus-goals-plus-habit tracker built as a live artifact replaces a separate journaling app for users who are already inside Claude daily.
- Live artifacts are paid-plan only — they require at least the $20/month Claude tier and are accessed through the Cowork desktop app.
- Building interactivity (filters, search, drill-downs, toggles) into a live artifact during initial creation saves re-prompting sessions later.
- Context window compaction happening silently inside Cowork is a real UX friction point — there is currently no visible indicator of how much context remains.
Steal the 'one micro-pattern, repeated seven times' structure.
The whole video is one three-beat loop — pain, demo, prompt — replayed seven times. Pick a primitive your audience just got access to, stack seven applications of it, and front-load the gotchas.
- Pick a new primitive (model, feature, MCP) your audience just got access to and could use today.
- Build 7 use cases that all follow the same three-beat micro-pattern — pain → dashboard tour → exact prompt. Don't vary the rhythm; viewers settle into it.
- Front-load 3-4 gotchas before any demo. 'It's local-only, no sharing yet, paid plan, silently compacts' — saying it up front buys trust for the rest of the video.
- End every use case with the exact prompt visible on screen. The prompt IS the gift; the dashboard is the proof.
- Specify aesthetic by reference — 'looks and feels like Stripe, Linear, Vercel.' Three brand names beat ten adjectives every time.
- Save the most surprising / most personal use case for last (his was the journal+habit+goals tracker). Recency-effect closer.
- Plug your offer mid-roll right after the highest-engagement use case, then echo at end-roll. Two soft beats > one hard pitch.
- Joe-relevant: build a JoeFlow 'morning command center' live artifact that pulls overnight transcripts + Batch run output + Sessions activity into one sidebar dashboard.
Terms worth knowing.
- Claude Artifacts
- Self-contained documents, dashboards, or interactive pages that Claude generates and displays in a side panel, separate from the chat thread.
- Live Artifacts (Claude Cowork)
- A Claude Cowork feature that lets users build persistent dashboards connected to external tools; the dashboard stays in the sidebar and pulls fresh data on demand without re-prompting.
- Claude Cowork
- Anthropic's desktop app for Claude that adds persistent projects, multi-session agent management, connector integrations, and live artifacts on top of the standard chat interface.
- Connectors (Claude Cowork)
- Pre-built or custom integrations — essentially MCP servers — that authorize Claude to read from or write to third-party tools like Gmail, Notion, Slack, or Stripe.
- MCP server
- A server implementing the Model Context Protocol that exposes an external tool or data source to an AI agent through a standardized interface.
- Zapier MCP
- A bridge that exposes Zapier's library of thousands of app integrations as a single MCP server, letting AI agents trigger automations across apps not natively supported by a connector directory.
- vidIQ MCP
- An MCP integration for the vidIQ YouTube analytics platform that allows Claude to query channel metrics, video performance data, and growth trends directly inside a conversation.
- Context window compaction
- An automatic process where Claude summarizes or trims older parts of a long conversation to free up space in the context window, allowing the session to continue without hitting the token limit.
- MRR (Monthly Recurring Revenue)
- The predictable revenue a business earns each month from active subscriptions or retainer clients, used as a core health metric for subscription-based businesses.
- Haiku 4.5
- Anthropic's lightweight, fast-response Claude model, optimized for speed and low cost rather than maximum reasoning depth.
Things they pointed at.
Lines you could clip.
“You build it once, it stays in your sidebar, and it pulls in fresh data from your actual tools every time you open it. No re-prompting needed.”
“Takes about five minutes to set that up if you've not already.”
“This is the kind of insight that changes what I decide to publish next week or even in a few days.”
“The simple truth is this — the thing that makes these different is, again, you build them once and they stay alive.”
“No re-prompting, no burning tokens to get the same dashboard every day.”
Word for word.
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
The bait, then the rug-pull.
Rick Mulready opens by killing the assumption: yes, you've seen Claude artifacts before — and that's exactly the problem. They go stale. You re-prompt. You burn tokens regenerating the same dashboard. Live artifacts flip that: build once, refresh on click, fresh data every time from your connected tools. The rest of the video is one tight loop run seven times — pain, dashboard tour, exact prompt — wrapped in a tutorial that's really a pitch for a new Claude primitive.
Named ideas worth stealing.
Three reasons live artifacts matter
- Persistence (sidebar across sessions)
- Interactivity (filters, search, drill-downs, toggles)
- Fresh data via connectors
Rick's framing of why this primitive is different from regular artifacts.
Four current limitations
- Local-only storage (doesn't follow you between devices)
- No sharing yet
- Paid plans only ($20+/mo Claude plan)
- No context-window indicator — silently compacts
Caveats stacked up front so the rest of the video isn't fighting objections.
Use-case loop
- State the pain
- Tour the finished dashboard
- Show the exact prompt
The same three-beat structure repeats verbatim across all 7 use cases.
Connector setup ladder
- Native Anthropic connectors (Gmail, Calendar, Slack, Notion, etc.)
- Custom MCP server URL
- Zapier MCP (8,000+ apps as fallback)
Three tiers of how to wire any app into Claude.
Format Pulling Weight tile
Custom dashboard widget comparing how much short-form vs long-form is contributing to subscriber growth. Outputs a recommendation ('prioritize depth over velocity').
How they asked for the click.
“If you're an online business owner and you're looking to leverage AI in your business and you're looking for the easy button, I've created an entire AI team that is at your disposal... all inside of my Zone of Genius app which all my members in the AI Playbook have access to. I'll link to it in the description below.”
Soft tie-back to the same product mentioned mid-roll. Frames the membership as 'the easy button' for the 80% of busy work — cleanly extends the video's thesis (don't re-prompt, build once) into the offer (don't build at all, use mine).







































































