Repository navigation
[ENG-4593] Say what to do when the install stops at ENOTFOUND registry.npmjs.org - #509
Merged
Merged
Conversation
Amp-Thread-ID: https://ampcode.com/threads/T-2e659ca3-7bd0-4d70-b3d3-09638251060b Co-authored-by: Danilo Radovic <danilo@patchstack.com>
|
🎯 Elite quality (98%) — Focused README troubleshooting section giving a concrete diagnostic and Codex sandbox fix for ENOTFOUND errors. 📦 Small 🤖 Written by Amp — going by its own attribution. Unknown whether a person read it; agents can report that with the ⚪ Minimal risk — only docs. ✅ No review needed |
Contributor
Author
|
/review |
mariojgt
approved these changes
Nov 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ref ENG-4593
What changed
A new README section, If the install stops at
ENOTFOUND registry.npmjs.org, after "If your coding tool blocks the command".In the dogfood round, Codex's sandbox could not reach the npm registry. npm failed before Connect was downloaded, and nothing told the tester where the fault was. The section:
npm pingas the check;network_accessunder[sandbox_workspace_write]) and the proxy/mirror settings to look at.The install prompt is unchanged, so
field-test/prompt.txtandGETTING-STARTED.mdare untouched.Checks
tests/install-prompt.test.tsandcapabilities:checkpass..vercelignorecase inbin-invocation, comes from a stale localdist/; it passes afternpm run build.The dashboard half of ENG-4593 (a prompt for local coding tools that matches the documented Claude Code allow rule, and a prompt without the key) is in patchstack/saas.
Flag: none — docs only.