How to Build Live Dashboards in Claude Cowork

TL;DR

Claude Cowork live artifacts can display current information from connected apps without requiring Claude to regenerate an entire static dashboard whenever the underlying data changes. In the desktop app, enable Cowork, select a working folder, connect services such as Gmail, Google Calendar, Google Drive, or Bitly, then describe the dashboard you want in a new task.

Transcript

Anthropic just dropped Claude Co live artifacts and this completely changes how I'm using it and I genuinely think not enough people are talking about how powerful this actually is. So in this video I'm going to break it down in simple terms so anyone can understand it and show you how you can begin using this right now. So without further ado, let... Read More

Key Insights

• Static HTML dashboards become stale because their displayed information does not change until Claude pulls the source data again and regenerates the dashboard. Repeating that process for email, calendars, analytics, or other frequently changing sources consumes additional tokens or credits.
• Live artifacts update their displayed information from connected applications without requiring the user to request a complete dashboard regeneration. The demonstrated morning artifact can populate newly received emails while also showing calendar events, priorities, and conversations that require attention.
• Claude connectors provide access to application data and actions used by live artifacts. The examples include retrieving Gmail messages, drafting email replies, reading Google Calendar events, accessing Google Drive, and combining information from services such as Notion, HubSpot, and Bitly.
• The Claude desktop app is required for the demonstrated Cowork workflow. After opening the app, the user enables Cowork with its sidebar toggle and selects or creates a working folder where projects, HTML dashboards, and related files will be stored.
• Live artifacts remain available from the Cowork sidebar after creation. This persistent access removes the need to search through previous conversations for a particular dashboard and provides a convenient place to reopen resources such as a skills library, analytics view, or morning inbox.
• A daily command center can combine inbox triage, Google Calendar meetings, and Bitly link performance in one interface. The example distinguishes urgent emails from messages that can wait and identifies which video links are driving traffic to the creator's community.
• Dashboard appearance can be customized through instructions given to Claude. The example uses an Anthropic-style theme because the creator previously configured that preference, but the transcript states that users can request any design they want for their own live artifacts.
• An MCP server can connect an application that is unavailable in Claude's native connector list. The demonstrated approach uses Zapier MCP, selects Cowork as the client, and adds tools for desired applications, although the transcript says this option is unnecessary when a native connector already exists.

Questions & Answers

Q: How do Claude Cowork live artifacts stay updated?

Claude Cowork live artifacts use connectors to draw information from linked applications and populate the artifact with current data. Unlike the static HTML dashboard described in the transcript, they do not require the user to ask Claude to scrape each source and regenerate the entire interface whenever information changes. The morning dashboard example can automatically display a newly received email alongside calendar events, priorities, and conversations requiring responses.

Q: How do I create a live dashboard in Claude Cowork?

Open the Claude desktop app, enable Cowork using the Cowork toggle, and select or create a working folder for the project files. Choose New Task and describe the dashboard in plain language, including the information sources and sections you want. In the example, the prompt requests categorized emails, Google Calendar meetings, and Bitly tracking information, producing a daily command center in about two minutes.

Q: Why are live artifacts better than static HTML dashboards?

Static HTML dashboards become outdated as soon as their source information changes. To refresh one, the user must ask Claude to retrieve the latest data and generate the dashboard again, which the transcript says wastes tokens or credits. Live artifacts solve that specific problem by using connected application data, allowing information such as new emails or changing link analytics to appear without repeatedly rebuilding the full dashboard.

Q: Which applications can supply data to live artifacts?

The transcript demonstrates or names Gmail, Google Calendar, Google Drive, Bitly, Notion, and HubSpot as applications that can work with Claude through connectors. These connections can provide emails, meetings, files, customer information, or link analytics for a live artifact. Available connectors can be reviewed by opening Customize, selecting Connectors, and choosing Browse Connectors inside the Claude desktop app.

Q: How do I connect Google Drive to Claude Cowork?

Open the left sidebar in the Claude desktop app and select Customize, which appears below Dispatch in the demonstrated interface. Select Connectors beneath Skills, then choose Browse Connectors and find Google Drive. Click Continue to grant access. After the connection is established, Cowork can pull information from Google Drive, and the transcript also says it can upload items to Google Drive on the user's behalf.

Q: What can a Claude Cowork daily command center include?

A daily command center can combine categorized email messages, urgent and nonurgent inbox items, Google Calendar meetings, Bitly link performance, top priorities, and ongoing conversations that require responses. The example is designed to reduce manual visits to separate applications. It also shows which video links attract the most clicks, helping the creator identify videos that drive traffic to a community and consider producing similar content.

Q: Where are live artifacts stored and reopened in Cowork?

Cowork stores project files and HTML dashboards in the working folder selected when the user enters Cowork mode. Generated live artifacts also appear in the left sidebar, where they can be opened without searching through old Claude conversations. The examples visible there include a library of 237 Claude skills, a Bitly analytics dashboard, and a morning inbox dashboard containing email and calendar information.

Q: How can I connect an app without a native Claude connector?

If the desired application does not appear in Claude's native connector list, the transcript recommends using an MCP server as an optional connection method. The demonstrated service is Zapier MCP, which is described as supporting more than 9,000 applications. The setup begins by adding a new MCP server, selecting Cowork as the client, choosing Add Tools, and searching for the application that needs to be connected.

Summary & Key Takeaways

• Static HTML dashboards become outdated and must be regenerated to display new information, consuming additional Claude tokens or credits. Live artifacts address this problem by drawing current information from connected applications. The demonstrated morning dashboard combines emails requiring responses, suggested priorities, calendar events, and ongoing conversations in one accessible interface.

• Creating a live artifact begins in the Claude desktop app. The user enables Cowork, selects a working folder for projects and files, and starts a new task describing the desired dashboard. Claude can then combine connected sources into a customized interface, such as a daily command center for email, meetings, and link performance.

• Connectors give live artifacts access to information and actions across applications such as Gmail, Google Calendar, Google Drive, Notion, HubSpot, and Bitly. They are managed under Customize and Connectors. When an application lacks a native connector, the transcript suggests using an MCP server, with Zapier MCP presented as one option.