RemoteTrigger: egress policy blocks legitimate domains (Openverse, Wikimedia, own domain) consistently for 4+ days

Product: Claude Code — RemoteTrigger
Type: network egress policy review request

Context

I use scheduled RemoteTriggers to auto-publish content to social media (via Metricool) for two brands. Some content formats need to download images from open-license image banks (Openverse, Wikimedia Commons) or download AI-generated image results (Higgsfield) before publishing.

Problem

I ran a diagnostic inside the RemoteTrigger sandbox itself (read /root/.ccr/README.md, tested connectivity to ~26 domains) and confirmed the egress policy consistently blocks (403 on CONNECT) the same set of domains for at least 4 days straight (2026-07-25 through 2026-07-28):

• Open-license image banks: api.openverse.org, commons.wikimedia.org, en.wikipedia.org, unsplash.com, pexels.com, pixabay.com (and subdomains)
• Higgsfield result CDN: d8j0ntlcm91z4.cloudfront.net
• My own publishing domain: ebooks.creatorup.online
• Even generic control domains: www.google.com, www.bing.com

Only these remain allowed: github.com, api.github.com, raw.githubusercontent.com, objects.githubusercontent.com, api.anthropic.com, registry.npmjs.org, pypi.org.

The README itself confirms there is no agent-side mechanism to change this list, and instructs reporting to support.

Request

Could the egress policy for this environment/organization be reviewed? Specifically requesting consideration to allow open-license image bank domains (legitimate, commercial-use-permitted, properly attributed) and my own domain (ebooks.creatorup.online).

As a workaround I have already moved the steps that depend on these domains out of RemoteTrigger (running them locally instead), but this limits the value of the cloud automation.