{"version":"2.1.292","anchor":"artifact-publish-gains-a-relay-only-path-that-refuses-to-sen","canonical_anchor":"artifact-publish-gains-a-relay-only-path-that-refuses-to-sen","heading":"Artifact publishing gains a relay-only mode that refuses to bypass the cloud session gateway","tier":"internal","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/artifact-publish-gains-a-relay-only-path-that-refuses-to-sen","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Artifact publishing gains a relay-only mode that refuses to bypass the cloud session gateway\n\nArtifact publish calls can now be relay-only, stopping with 'Nothing was published' instead of falling back when the cloud session gateway cannot carry them\n\n**Unclear.** It is not clear when Claude Code uses the relay-only mode, or whether any build turns it on.\n\n**What**\n\nArtifact 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.\"\n\nA helper also spells out when a publish does not count as one \"made without asking\":\n\n- it names an existing artifact\n\n- it sets force\n\n- it declares capabilities\n\n- it removes files\n\n- it makes a live file\n\nSeparately, 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.\n\n**Why**\n\nIn 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.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}