Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] No Claude Environment Selector in Claude Code Routines, so cannot access Network APIs.

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Error Messages/Logs

Root Cause

HTTP 403 x-deny-reason: host_not_allowed Body: Host not in allowlist The certificate issuer in the curl output above is CN=Egress Gateway Subordinate CA — that's Anthropic's TLS inspection proxy. It allows the connection but blocks the request because emailmanager.aiassists.me is not on its approved host list.

Code Example

Blocker 1: Network allowlist (the actual blocker)
The TLS handshake succeeds, but Anthropic's egress proxy intercepts it and returns:

HTTP 403  x-deny-reason: host_not_allowed
Body: Host not in allowlist
The certificate issuer in the curl output above is CN=Egress Gateway Subordinate CA — that's Anthropic's TLS inspection proxy. It allows the connection but blocks the request because emailmanager.aiassists.me is not on its approved host list.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

When running a Claude Code Routine what harnesses an API, there is no Claude Environment selector to select the environment config already setup in the Claude Console - its missing. This is fundamentally required so that the API setup in the Routine can authenticate and reach the environment config's authorised Domain. The Claude Routine therefore will always fail since the API is "unreachable" due to the domain rejection which would be resolved if the Claude Environment selector was not missing and thus available for selection in the Claude Routine editor.

What Should Happen?

Claude Environment Selector in the Claude Routine should exist and attach to the Routine. As a Feature request Credentials could also attach for env vars.

Error Messages/Logs

Blocker 1: Network allowlist (the actual blocker)
The TLS handshake succeeds, but Anthropic's egress proxy intercepts it and returns:

HTTP 403  x-deny-reason: host_not_allowed
Body: Host not in allowlist
The certificate issuer in the curl output above is CN=Egress Gateway Subordinate CA — that's Anthropic's TLS inspection proxy. It allows the connection but blocks the request because emailmanager.aiassists.me is not on its approved host list.

Steps to Reproduce

  1. Create any Routine with an API and credentials outside of Claude's allowlist e.g. *.aiassists.me and run the routine.

The Routine will fail to reach the API host saying the API host is unreachable as the domain is not in the allow list, which it is inside a Claude Environment but the environment is not associated with the Routine.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.119

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#retrieval issue#search optimization#API routing#API middleware

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING