[FEATURE] Add npm.cloudsmith.io to allowed egress hosts for Claude Code Web

Resolved 💬 3 comments Opened Feb 25, 2026 by hatoya Closed Feb 28, 2026

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

When using Claude Code Web, npm ci fails with a 403 Forbidden error when trying to install packages from npm.cloudsmith.io (Cloudsmith private registry).

This is because npm.cloudsmith.io is not included in the allowed_hosts list of the egress control proxy JWT.

Proposed Solution

npm ci should be able to fetch packages from npm.cloudsmith.io, as it is a widely used package registry (used by Web Awesome / Font Awesome).
Please add npm.cloudsmith.io (and ideally *.cloudsmith.io) to the default allowed egress hosts list.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

  1. Configure .npmrc with a Cloudsmith-hosted private registry:
@awesome.me:registry=https://npm.cloudsmith.io/fortawesome/webawesome-pro
//npm.cloudsmith.io/fortawesome/webawesome-pro/:_authToken=<token>
  1. Run npm ci in a Claude Code Web session
  2. Observe the error:
npm error code E403
npm error 403 403 Forbidden - GET https://npm.cloudsmith.io/fortawesome/webawesome-pro/@awesome.me/webawesome-pro/-/webawesome-pro-3.2.1.tgz

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗