iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Anthropic engineer Thariq Shihipar has encouraged people to use Claude Artifacts as project dashboards—not as a blanket recommendation for every task. In a Latent Space interview, he described dashboard-style Artifacts as a way to keep project information, such as a Kanban board’s state, available to both people and Claude. He also presented the workflow as an emerging direction, not a guaranteed capability for every user or project.
What are Claude Artifacts?
Anthropic describes Artifacts as self-contained content, apps, tools, and other outputs made with Claude. They are intended for work you may want to edit, refine, reuse, or share separately from the conversation. You can ask Claude to create an Artifact and continue working with that output as its own item. See Anthropic’s current Artifacts documentation for the feature’s present behavior and availability.
![Claude AI for Beginners Bible: [5 in 1] The Ultimate Guide to Automate Your Work, Save Hours Every Week, and Use AI for Real-World Results](https://m.media-amazon.com/images/I/415+fSJacsL._SL160_.jpg)
That general description explains what the feature is; it does not establish Shihipar’s specific recommendation. His dashboard idea is a particular way of using the feature for ongoing work.
What did Thariq Shihipar recommend?
In the Latent Space interview transcript, Shihipar said: “one thing that, like, people are not doing yet that I’m trying to, like, encourage is this idea of a dashboard artifact.” He discussed using a dashboard to keep persistent project information—such as Kanban state—available to Claude and the people working on the project. The conversation also framed this kind of interface as a possible way to support planning and interaction between people and agents.
#1 Best Overall
This is Shihipar’s view expressed in an interview, not a formal Anthropic promise, product roadmap commitment, or instruction to use Artifacts for every Claude task. The interview characterizes the supporting infrastructure as still developing. The Latent Space transcript is the source for his comments; Behind the Craft’s episode notes identify the discussion as an interview with Shihipar about planning and building with Claude Code.
When could a dashboard Artifact help?
A dashboard is worth considering when a project has a state that needs to be consulted and updated over time. Shihipar’s examples point to situations such as a long-running project, a shared plan, or a Kanban-style tracker. Rather than repeatedly reconstructing the project’s status from conversation history, a dashboard could give collaborators a distinct place to see the working state and make it available to Claude.
Whether that approach suits a project depends on the work, not simply on whether an Artifact can be created:
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall- State persistence: Does the project’s status need to remain visible across work sessions, or is it temporary context for one exchange?
- Format: Would an interactive board or tool be useful, or is a readable document enough?
- Shared access: Do several people or agents need to consult the same project information?
- Availability: Does the workflow rely on a specific Claude plan, setting, or capability that may not be available to everyone?
These are practical decision points, not a tested comparison showing that dashboards outperform notes, documents, or other ways of tracking work.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Does an Artifact keep project information between sessions?
Shihipar described persistent project data as a reason to use a dashboard-style Artifact, but that interview does not establish that every Artifact automatically preserves or supplies project state across sessions. Anthropic’s help page is the appropriate source for current feature behavior; check it before relying on a particular persistence, sharing, or access workflow. A dashboard concept should not be treated as a guarantee that Claude will always retain or retrieve project information without the relevant feature support and setup.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
