/artifacts in Claude Code: pick up any artifact in a new session

New session, the link scrolled away, you ask for a change: Claude publishes a fresh artifact instead of touching yours. One command lists yours and the ones shared with you, and Enter makes the session keep editing the one you had.

The /artifacts panel in Claude Code: Enter attaches an artifact to the new session and the publish lands on the same link; without attaching, Claude creates a second artifact

TL;DR /artifacts, select, Enter. From then on, "update the dashboard" republishes to the same link instead of creating another one. o opens it, c copies the URL, d deletes it, / searches. Ctrl+] only reopens the latest artifact of the current session.

An artifact outlives the session that published it. The session does not: you close the terminal, run /clear, or come back the next day, and the link is no longer on screen. Ask for a change in that new session without more context and Claude leaves your artifact alone. It publishes another one.

I checked this with two contexts working on the same file. One got the artifact URL plus a change request; the other got only the change:

With URL:     Published deploy-failures.html at https://claude.ai/code/artifact/1c74efc6-...
Without URL:  Published deploy-failures.html at https://claude.ai/code/artifact/9dc0883b-...

Same page, two artifacts. In the gallery, two identical "Deploy Failures" entries stacked on top of each other. The tool itself says so on every publish: without the URL, a conversation that did not publish that artifact creates a separate one.

The command

/artifacts opens, inside the terminal, the list of every artifact you own and every one shared with you, read from your claude.ai account. It works in a new session and after /clear, which is exactly when the link is gone. Illustrative preview (the panel is interactive and changes with the version):

/artifacts

  All 6   mine 6   shared 0

❯ 📊 Deploy Failures          updated today
  📊 Deploy Failures          updated today
  🛠️ Craft 3.0                updated today
  🧾 Cuentas con Amalia       updated 5 days ago
  🎛️ Simulador                updated 26 days ago

  enter attach · o open · c copy url · d delete · / search · r refresh

Enter is the key that fixes the problem at the top: it attaches the artifact to the current session. From that point Claude knows which URL it is working on, pulls the published content and republishes there, at the same address, as a new version. Every publish is a version, and the Share control on the page lets you choose which one viewers see. Before v2.1.216, Enter opened the artifact in the browser; attaching is the new part.

The no-panel alternative is pasting the URL into the prompt ("Update https://claude.ai/code/artifact/… with today's numbers"), which is what I did in the test above. Fine when you have the link at hand. The command exists for when you don't.

The keys

The official docs list three (o, c, Enter). On v2.1.261 the panel answers to quite a few more; I pulled them from the binary itself:

Key	What it does
Enter	Attaches the artifact to the session (the session now edits that one)
`o`	Opens it in the browser
`c`	Copies the URL
`d`	Deletes it, with a `y` / `n` confirmation
`/`	Filters the list by title
`p`	Pins it to the top of the list, where your panel offers it
Ctrl+R	Renames it
`x`	Detaches it from the session
`r`	Reloads the list

Tabs at the top switch between all, yours, shared with you, and pinned. The list sorts by last viewed, pinned first. Deleting with d is what cleans up the duplicate from the example, because there is no way to remove an artifact from the chat.

Ctrl+] is not a substitute for the panel. It reopens the latest artifact of the current session (the app:openArtifact action, rebindable in your keybindings). A new session has no "latest": that is where /artifacts comes in.

With a team

The "shared" tab lists what others shared with you. On Team and Enterprise, when someone makes you an editor of their artifact you pick it up the same way: /artifacts, Enter, republish from your session. And when you share inside the organization, the comments people leave on the page can reach Claude so it replies or applies the changes (Send to Claude, or @claude in the thread; v2.1.221+). I could not test that on my plan, so I defer to the docs there.

Whether what you are picking up is a /design canvas or the artifact you use to understand what you delegate, the flow is the same: they are artifacts.

Official docs: Find an artifact again · Update an artifact

Requirements

/artifacts since v2.1.208; Enter attaches since v2.1.216. Extra keys observed on v2.1.261.
A session signed in with /login on a Pro, Max, Team, or Enterprise plan. No artifacts with an API key, a gateway, or Bedrock, and none in claude -p either: in print mode the tool does not load (tested twice).