🖼️ Some answers are easier to look at than to read.
Sometimes you need to “see” the data or the thing that Claude Code is working on. Fortunately, Claude Code can publish what it calls an “artifact”—a live web page accessible via claude.ai, built… well, built by Claude! This can be especially useful when plain terminal text isn’t the best way to show something.
Maybe you want to see a git diff annotated inline, or a dashboard of the data the session is already working on. Maybe just prototype a few different layouts to see what you like (sometimes seeing is believing).
You can just ask Claude to “show that graph in an artifact.” Sometimes it will do it on its own, but that happens less often in Claude Code than in the desktop chat.
One of the best things here is that Claude can keep iterating on the same page, so you don’t end up with a pile of different links, and you can even share the pages with folks in your organization (for Team and Enterprise plans) or (😱) with a public link.
One underrated bit is that your teammates can leave comments, and you can jump back to your Claude thread to answer or update the artifact. Anyone with edit access can also mention @claude in a comment thread to have Claude reply there.
HT: Tim Rawson
P.S. An artifact is still one self-contained page with no backend, so it can't host an app.
P.P.S. Roscoe sent this one in, Claude drafted it from the docs, and Claude somehow resisted the urge to turn this post into an artifact (And wrote this PPS).