What Artifacts are (and why they show up in the right panel)
The panel where Claude puts things you are meant to use
After this, you'll be able to tell a normal chat reply apart from an Artifact. You'll know why some outputs open in the right-hand panel, and you'll ask for an Artifact on purpose.
Before you start
Complete Your first real conversation first; this lesson builds on the direct-and-refine habit taught there, because Artifacts are produced and reshaped through that same back-and-forth.
The idea
An Artifact is something Claude makes for you to use, not just read. It opens in a panel on the right, separate from the chat thread. Think of the chat as the conversation and that panel as the workbench, where Claude puts anything long, structured, or interactive enough to work with on its own.
Here is the before and after: Ask "what should go in a project status update?" and Claude answers inside the chat. Ask "write me a project status update I can send to my manager" and a document opens in the panel, with its own copy and export buttons.
Now try it: open claude.ai and send "Write a one-page meeting agenda for a 30-minute team sync, formatted so I can paste it into an email." Watch for the panel to slide in from the right; that opening is the signal Claude made an Artifact.
When output opens in the right panel, treat it as a finished thing to use, not a reply to read.
Try it (8 min)
Watch out for
- Looking for the Artifact inside the chat thread and missing it; the panel opens on the right, separate from your messages
- Assuming every reply is an Artifact; short answers and explanations stay in the chat on purpose
- Closing the panel by accident and thinking the Artifact is gone; it stays attached to that message and you can reopen it
- Asking a vague question and being surprised you got a chat reply instead of a document; name the deliverable to get an Artifact
- Trying this in a tool that is not claude.ai or the Claude desktop app and not seeing a panel; the Artifact panel is a Claude feature
Paste this into Claude
I want to see the difference between a normal reply and an Artifact. First, answer this in the chat as a short reply: in one sentence, what makes a good project status update? Then, separately, create a finished document I can use: write a one-page project status update for a project called "Website Redesign." Include sections for Progress This Week, Blockers, and Next Steps. Format it so I can copy it straight into an email to my manager. After you make the document, tell me in plain English why the second request became an Artifact and the first one stayed in the chat.
What good looks like
- The first answer stayed in the chat as a short reply with no panel opening
- The second request opened a document in the panel on the right side of the screen
- The status update has all three sections: Progress This Week, Blockers, Next Steps
- Claude explained in plain English why the document became an Artifact and the sentence did not
- You found the copy or export control on the Artifact panel
When this breaks
- Breaks when you treat the panel as decoration because you then ignore the copy and export buttons that make the output usable, and you retype work Claude already finished.
- Breaks when you expect an Artifact for every reply because Claude only pulls output into the panel when it is something you will use on its own, so a question that wants an explanation gets an explanation, not a document.
AI can help with this
Open claude.ai and paste this, filling in the bracket: 'Create a finished document I can send to someone: write a [meeting agenda / status update / short proposal] about [your topic]. Format it so I can copy it straight into an email.' Watch the panel open on the right; that is your Artifact.
You can now
You can complete the lesson outcome in a real Claude chat, Project, Artifact, Connector, Desktop, or Code surface.
- You can verify that the first answer stayed in the chat as a short reply with no panel opening.
- You can verify that the second request opened a document in the panel on the right side of the screen.
- You can verify that the status update has all three sections: Progress This Week, Blockers, Next Steps.
- You can verify that claude explained in plain English why the document became an Artifact and the sentence did not.
Key takeaways
The Artifact panel is Claude's workbench: when output opens on the right, it is a thing you are meant to copy, edit, or share, not just read. Naming the deliverable is how you ask for one on purpose.
- Recognize an Artifact by the panel that opens on the right, separate from the chat thread.
- Treat anything in the panel as a finished thing to copy, download, edit, or share.
- Trigger an Artifact on purpose by naming the deliverable, not asking a vague question.
- Expect explanations and short answers to stay in the chat; only usable outputs get the panel.
- Find the copy and export controls in the panel; that is where the output leaves the conversation.
Go deeper