What
The Artifacts tool now documents a preview action. Given a file_path pointing at a page file, it renders that one file locally the same way publish would wrap it, and returns:
- Screenshots in both light and dark themes
- Screenshots at desktop and phone widths
- A checklist noting any layout or load problems found
This happens before publishing, and it does not need an artifact URL or the artifact runtime, so any capability code in the file does not actually run during preview.
Why
This lets a page be checked for how it looks and whether it loads cleanly across themes and screen sizes before it goes live as a published artifact, without wiring up a real runtime environment first.
Names in the bundlepreview
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.
Added since
A small documentation edit on Archive a Dream touched a line naming preview after this was published.
The Dreams API is in research preview: the request and response shapes are volatile and may change without the deprecation period that applies to generally-available endpoints.api/beta/dreams/archive see the edit
Confirmed since
Anthropic's documentation has since written up preview, on Admin controls.
* **Your own systems and data**, such as an internal database or lab system: have your developers build a connector for it, then add its web address for everyone under **Organization settings > Connectors > Add > Custom** (see [Third party…claude-science/admin-controls see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up preview, on Admin controls.
Anthropic's release notes agree
Fixed Write calls failing validation when a model sends path, file_text, file_content or a stray description instead of file_path and…