What
Artifacts are files or pages Claude can publish for you. Publishing them changed in two connected ways:
- New helpers fetch artifact content from
/api/frame/content/...with anx-frame-asset-tokenheader. They retry on 429 and 503 errors and accept the response only whenx-frame-content-routeis "served". - This path is used when
contentVia === "frame"and is skipped whenCLAUDE_CODE_REMOTEis set. - The deploy function takes a new flag. When a later send of a publish is cancelled or the cloud session's gateway fails, it now reports 'a later send of this publish could not go through the cloud session's gateway'. Before, failures only said 'relay request failed' or 'deploy request failed'.
- The relay code now uses a shared helper for working out content types, which used to be defined locally.
Why
When publishing an artifact from a cloud session fails part way, the message now says where it went wrong. Busy or briefly unavailable servers are retried instead of failing straight away.
Names in the bundleCLAUDE_CODE_REMOTE
Documented inclaude-code/cloud-environments
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.
Confirmed since
Anthropic's documentation has since written up CLAUDE_CODE_REMOTE, on Customize sessions in self-hosted environments.
| `CLAUDE_CODE_REMOTE_SLACK_THREAD_URL` | For a [Claude Tag](https://claude.com/docs/claude-tag/overview) session that belongs to one Slack thread, the link to that thread. Unset for other sessions, and can be unset for a thread session to…self-hosted-environments-configuration see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up CLAUDE_CODE_REMOTE, on Customize sessions in self-hosted environments.