You'll notice
Useful2 Signal3
Refused artifact asset reads now say where such reads work, and public assets skip the gate.
What's wrong with this entry?
Anonymous. No account, no email.
What
The refusal shown when an artifact asset cannot be read now states exactly where such reads work: a local session, or an Anthropic-hosted cloud session with its gateway relay enabled. Reads of public assets are no longer subject to the same access gate as private ones.
Details
- The message ends "retrying from here will not help", so there is no point re-running.
- Detection of a remote session moved from an inline environment-variable test to a shared helper.
Evidence
asset reads run only from a local session or an Anthropic-hosted cloud session with its gateway relay enabled; retrying from here will not help
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.