Unclear What decides whether the in-app frame viewer is used instead of /artifacts is not stated.
Selecting the frame item in the footer (the status line at the bottom of the screen) used to always run /artifacts. Claude Code now first checks whether an in-app frame viewer is available:
- With several frames, it opens a picker so you can choose one.
- With a single frame, it opens that frame directly.
- Without the viewer, it runs
/artifactsas before.
The hint shown in the footer is no longer always "view artifacts" and now varies.
Artifact links can open inside Claude Code instead of going through a slash command.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Product that produced this row's activity: one of `chat`, `claude_code`, `cowork`, `office_agent`, or `chat_cowork_unified` (Chat and Cowork unified). These are the canonical Cost & Usage product names; an `office_agent` row's per-surface …api/beta/organization/analytics/apps see the edit
Product that produced this row's activity: one of `chat`, `claude_code`, `cowork`, `office_agent`, or `chat_cowork_unified` (Chat and Cowork unified). These are the canonical Cost & Usage product names; an `office_agent` row's per-surface …api/beta see the edit
What decides whether the in-app frame viewer is used instead of `/artifacts` is not stated.
Anthropic's documentation has since written up /artifacts, on Beta.