Skip to content

Say what to do when an AI assistant blocks the Connect install - #103

Merged
daniloradovic merged 1 commit into
mainfrom
danilo/eng-4094-update-patchstack-connect-troubleshooting-docs-for-claude
Sep 30, 2026
Merged

daniloradovic merged 1 commit into
mainfrom
danilo/eng-4094-update-patchstack-connect-troubleshooting-docs-for-claude

Conversation

@daniloradovic

Copy link
Copy Markdown
Contributor

Closes ENG-4094.

During the Patchstack Connect end-to-end testing, Claude Code blocked npm install @patchstack/connect in one run and npx @patchstack/connect setup in another. Replying "you have permission to run the command" did not lift the block.

Changes

  • New page: Getting Started → Installing Patchstack → AI assistant blocked a command (/getting-started/installing-patchstack/ai-assistant-blocked-a-command/)
    • Running the blocked command yourself is fine. Links to the existing security and data handling section.
    • Claude Code: run the command with the ! prefix (install, setup, or setup --claim-token), then let Claude continue. Includes a follow-up prompt and protect --check for server apps.
    • Optional .claude/settings.json allow rule Bash(npx @patchstack/connect:*).
    • Other assistants and site builders: run it in a terminal and paste the output back.
  • Links to the new page from the install page, JS/Node troubleshooting, Adding a site (AI-assisted), and Pulse overview.
  • FAQ → Errors entry that points to the new page, so the answer can also be found from the FAQ.

Worth checking

  • Nobody has tested whether the allow rule gets past Claude Code's auto mode classifier. Claude suggested it in Renato's run.
  • The claim-token command comes from the existing install docs, not from the testing thread.

🤖 Generated with Claude Code

Claude Code's permission checks can stop `npm install` or
`npx @patchstack/connect setup` part-way through an install, and replying
"you have permission" often does not lift the block. A new page under
Installing Patchstack says running the command yourself is fine, shows how
to do it in Claude Code with the `!` prefix, and covers other assistants.
The install, JS/Node troubleshooting, Adding a site and Pulse overview
pages link to it, and an FAQ Errors entry points there.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
@coderbuds

coderbuds Bot commented Sep 30, 2026

Copy link
Copy Markdown

Well-focused documentation updates clearly address AI assistant install blocks.

🎯 Quality: 96% Elite · 📦 Size: Medium

📈 This month: Your 212th PR — above team average · Averaging Excellent

See how your team is trending →

@netlify

netlify Bot commented Sep 30, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for deluxe-meerkat-8daf24 ready!

Name Link
🔨 Latest commit b44631b
🔍 Latest deploy log https://app.netlify.com/projects/deluxe-meerkat-8daf24/deploys/6abd086a6d6a780008c8ae6e
😎 Deploy Preview https://deploy-preview-103--deluxe-meerkat-8daf24.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@daniloradovic

Copy link
Copy Markdown
Contributor Author

/review

@daniloradovic
daniloradovic merged commit 2694728 into main Sep 30, 2026
4 checks passed
@daniloradovic
daniloradovic deleted the danilo/eng-4094-update-patchstack-connect-troubleshooting-docs-for-claude branch September 30, 2026 13:41
claude Bot pushed a commit that referenced this pull request Sep 30, 2026
Bring in #103 (AI assistant blocked a Connect command). Its edit to the
old Pulse overview page carries over to Patchstack for JS/overview.md.
In adding-a-site.mdx, keep main's new sentence and the renamed
Patchstack for JavaScript overview link.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01Ustuxckjeo5Gkofas6tPXQ
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants