diff --git a/src/content/docs/Getting Started/Installing Patchstack/ai-assistant-blocked-a-command.mdx b/src/content/docs/Getting Started/Installing Patchstack/ai-assistant-blocked-a-command.mdx index 399c26c..03ee860 100644 --- a/src/content/docs/Getting Started/Installing Patchstack/ai-assistant-blocked-a-command.mdx +++ b/src/content/docs/Getting Started/Installing Patchstack/ai-assistant-blocked-a-command.mdx @@ -90,6 +90,8 @@ If you would rather Claude Code ran the Connect commands itself — for example Add the rule yourself. Claude Code will usually decline to edit its own permissions to get past a check that has just stopped it. +The rule matches the command text as written, so it only covers a command that starts with `npx @patchstack/connect`. A command with `PATCHSTACK_ENVIRONMENT=sandbox` in front of it is not covered. That label is for online builders; on your own machine choose **On my computer** when you copy the message in the Patchstack App, and the command in it starts with `npx`. + ## In other assistants and site builders Codex, OpenCode, Gemini CLI, Cursor and the rest each have their own approval settings, but the fix is the same: run the blocked command yourself from the project folder, then tell the assistant it has been run. @@ -104,6 +106,10 @@ Codex, OpenCode, Gemini CLI, Cursor and the rest each have their own approval se Site builders such as Lovable, GoDaddy Airo and Hostinger Horizons do not always give you a terminal. If yours has none and the assistant cannot run the install, ask it to name the exact step it cannot perform — the [builder context](/getting-started/installing-patchstack/troubleshooting-javascript-node-projects/#tell-your-builder-what-project-this-is) snippets help with that. +## The install stops at `ENOTFOUND registry.npmjs.org` + +That error comes from npm, before Patchstack is downloaded: the assistant's workspace cannot reach the npm registry. Some coding tools run commands in a sandbox with network access off. Run `npm ping` to check. 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` in the same shell. Then run the install again. + ## Still stuck? - `npx @patchstack/connect guide` prints a project-aware checklist of what is present and what is missing, so you can see how far the install got. diff --git a/src/content/docs/Patchstack App/Sites/adding-a-site.mdx b/src/content/docs/Patchstack App/Sites/adding-a-site.mdx index 3dccb1d..94dd67c 100644 --- a/src/content/docs/Patchstack App/Sites/adding-a-site.mdx +++ b/src/content/docs/Patchstack App/Sites/adding-a-site.mdx @@ -24,6 +24,6 @@ Adding a site to Patchstack is relatively easy. Here is a simple guide on how to 8. Upload the plugin .zip file to your WordPress site by visiting /wp-admin > Plugins > Add New > Upload Plugin 9. Activate the plugin -**JavaScript and Node.js projects do not need this flow.** Select **AI-built** from the platform list instead and copy the message the app shows you into the assistant that built your website. The assistant installs [`@patchstack/connect`](/getting-started/installing-patchstack/installing-on-javascript-node-projects/) and hands you back a link; paste it into the same panel to attach the site to your account. Tick **Connect this website to my account automatically** before copying and the message carries a one-day key for your account instead: the site is then created already attached to you, and the panel notices it by itself with nothing to paste. If the assistant still hands you a link (a message copied yesterday no longer connects), the paste field works as before. If the assistant refuses to run the install, see [My AI assistant blocked a Connect command](/getting-started/installing-patchstack/ai-assistant-blocked-a-command/). See [Patchstack for JavaScript sites overview](/patchstack-app/patchstack-for-javascript/overview/) for what those sites look like in the app. +**JavaScript and Node.js projects do not need this flow.** Select **AI-built** from the platform list instead, choose where you build — **Online builder** (Lovable, Bolt, v0, Replit) or **On my computer** (Claude Code, Cursor, Codex) — and copy the message the app shows you into the assistant that built your website. The assistant installs [`@patchstack/connect`](/getting-started/installing-patchstack/installing-on-javascript-node-projects/) and hands you back a link; paste it into the same panel to attach the site to your account. Tick **Connect this website to my account automatically** before copying and the message carries a one-day key for your account instead: the site is then created already attached to you, and the panel notices it by itself with nothing to paste. If the assistant still hands you a link (a message copied yesterday no longer connects), the paste field works as before. Some assistants refuse any message that carries a key: when the panel copies the key into the message for you, **My assistant won't accept the key** switches back to the message without it and the paste field. If the assistant refuses to run the install, see [My AI assistant blocked a Connect command](/getting-started/installing-patchstack/ai-assistant-blocked-a-command/). See [Patchstack for JavaScript sites overview](/patchstack-app/patchstack-for-javascript/overview/) for what those sites look like in the app. If you need further help, don't hesitate to reach out to us via live chat at the bottom right corner! \ No newline at end of file