From 89e10cc889186481e85f23feed795b7e1d054602 Mon Sep 17 00:00:00 2001 From: Amp Date: Fri, 20 Nov 2026 10:17:41 +0000 Subject: [PATCH] Say what to do when the install stops at ENOTFOUND registry.npmjs.org Amp-Thread-ID: https://ampcode.com/threads/T-2e659ca3-7bd0-4d70-b3d3-09638251060b Co-authored-by: Danilo Radovic --- README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/README.md b/README.md index 5d1249a..096f578 100644 --- a/README.md +++ b/README.md @@ -110,6 +110,19 @@ you how to proceed. Any of these works: Codex CLI asks according to `approval_policy` in `~/.codex/config.toml`: approve the command when it asks, or run it yourself. +### If the install stops at `ENOTFOUND registry.npmjs.org` + +That error comes from npm, before Connect is downloaded: the workspace cannot reach the npm registry. Some +coding tools run commands in a sandbox with network access off by default; Codex CLI's `workspace-write` +sandbox is one. `npm ping` shows whether the registry answers. If it does not: + +- In Codex CLI, set `network_access = true` under `[sandbox_workspace_write]` in `~/.codex/config.toml`, or + approve the install to run outside the sandbox when Codex asks. +- Behind a company proxy or registry mirror, check `npm config get registry` and the `proxy` and + `https-proxy` settings in the same shell the assistant uses. + +Then run the install again. + ### Claude Code plugin In Claude Code, install the plugin from this repository's marketplace: