[FEATURE]
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
In Claude Code web sessions, the egress proxy (127.0.0.1:33705) returns
403 for the following hosts, making it impossible to call these APIs:
- backboard.railway.app:443 (Railway GraphQL API)
- uptime.betterstack.com:443 (Better Stack uptime monitoring API)
Proxy status confirms these are policy denials (connect_rejected),
not TLS or tool configuration issues.
Use case: querying Railway service health and deployment status
directly from a Claude Code web session without needing a local CLI.
Request: add these hosts to the allowed egress policy for web sessions.
Best regards,
Viking Kjellstrom
Proposed Solution
In Claude Code web sessions, the egress proxy (127.0.0.1:33705) returns
403 for the following hosts, making it impossible to call these APIs:
- backboard.railway.app:443 (Railway GraphQL API)
- uptime.betterstack.com:443 (Better Stack uptime monitoring API)
Proxy status confirms these are policy denials (connect_rejected),
not TLS or tool configuration issues.
Use case: querying Railway service health and deployment status
directly from a Claude Code web session without needing a local CLI.
Request: add these hosts to the allowed egress policy for web sessions.
Best regards,
Viking Kjellstrom
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
API and model interactions
Use Case Example
_No response_
Additional Context
_No response_