Unclear It is not clear when Claude Code uses the relay-only mode, or whether any build turns it on.
What
Artifact publish, reserve and upload calls now take an optional relay-only argument (relayOnly). When it is set, the request is sent only through the cloud session's gateway, the connection point a cloud session uses to reach outside services. If the gateway cannot carry the request, Claude Code does not fall back to another route. It stops and reports: "Nothing was published: a publish made without asking must go through the cloud session's gateway, which could not carry it. Publishing it again now goes through the usual permission check, which may need a person's approval."
A helper also spells out when a publish does not count as one "made without asking":
- it names an existing artifact
- it sets force
- it declares capabilities
- it removes files
- it makes a live file
Separately, the plugin-prune warning has a new case for a file that was not read because of its path, telling you to replace any link to another machine on that path with a real file or folder.
Why
In cloud sessions, a publish that was not explicitly approved can no longer go out by a route other than the gateway. If it fails, publishing again goes through the normal permission check, which may ask a person to approve it.
It is not clear when Claude Code uses the relay-only mode, or whether any build turns it on.