Move a result into a surface that can be inspected, revised, and shared deliberately.
Conversation & research · Changing · Documentation checked 2026-10-04
Claude apps, projects, and Cowork; Claude Code and Claude Platform are separate environments.
Current Artifacts require cloud code execution / file creation. Templates are beta on paid plans; some editing and sharing controls require web or desktop.
The worked example is illustrative and has not been tested in a signed-in product account.
What it does and how it connects
Move a result into a surface that can be inspected, revised, and shared deliberately.
An Artifact is an editable output surface rather than only a chat response. Current documentation describes documents, designs, slides, dashboards, and interactive work. Paid template experiences are beta, and older pre-September artifacts behave differently. Treat editing, publishing, and connected storage as separate decisions.
Walkthrough
Use the product named in the access panel. The steps below combine documented controls with the editorial example.
- Enable cloud code execution and file creation if the account permits it.
- Ask for a specific inspectable deliverable; select a supported template only if available.
- Revise one part at a time and inspect the preview or output file.
- Review access and data behavior before sharing an Artifact or connecting an app.
Worked example
Create a one-page workshop handout from approved notes. Inspect definitions and heading order, then request a focused rewrite of the agent example. An interactive handout should not quietly collect participant information.
Create an editable one-page handout from the attached workshop notes. Include models, assistants, workflows, and agents; preserve the approved definitions. Use headings readable on a phone. No account connections, data collection, or publication. Flag any factual additions for my review.
Inspect and verify the result
Open the actual deliverable. Check all visible text, exported formatting, links, keyboard access, and any app behavior. If interactive content stores data, inspect what is stored and who can access it before sharing.
Limits and troubleshooting
Current Artifacts require enabled capabilities; templates have paid-plan and administrative conditions. Mobile viewing and creation do not imply all web editing or sharing controls. If an older artifact cannot be recreated in the same form, follow the new documented surface.
Data, permissions, and actions
An Artifact may contain copied source information. Sharing can expose it beyond the original chat. Connected apps and persistent data introduce additional account and retention boundaries; do not infer those permissions from a preview.
Related reading
Skills, plugins, connectors, and MCP
Connect a reusable procedure to narrowly authorized external information or tools.
From reports to an editable briefing
Build a private Artifact from a bounded source set and a verified argument.
A bounded Cowork preparation task
Use an eligible agent to prepare a workshop pack while preserving original files.
Evaluations: does the system do the job?
Create representative tests for quality, tool behavior, refusal, escalation, and the effects of a change.
Sources and verification
Documentation checked 2026-10-04. Examples are illustrative unless described otherwise.
Artifacts and current editing surfaces · Anthropic