Skip to content

[NO-TICKET] Tell agents to give Patchstack the live address when the host does not - #338

Merged
mariojgt merged 1 commit into
mainfrom
docs/confirm-deploy-without-heartbeat
Oct 1, 2026
Merged

mariojgt merged 1 commit into
mainfrom
docs/confirm-deploy-without-heartbeat

Conversation

@mariojgt

@mariojgt mariojgt commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

What changed

AGENT-INSTALL.md → "Deploying" gets one new item: give Patchstack the live address when the host doesn't. On any host other than Vercel, Netlify, Render and Railway (which report their production address themselves), the agent takes the public address from the deploy output or asks the person. It then:

  1. adds it to .patchstackrc.json as "url";
  2. runs npx @patchstack/connect scan once.

Why

Patchstack confirms a deploy by reading the build marker off the live page. It does that either when a visitor's browser loads the widget, or through its own scheduled check of the site's address. A new site can go days without a visitor, so the scheduled check is often the only confirmation, and it can only read an address Patchstack has.

Most hosts don't report one: ChatGPT Sites, Lovable, Bolt, custom domains, GitHub Pages, Cloudflare Pages and hand uploads. The guide never told the agent to provide it, so those sites sat on a placeholder or a preview address with no way to confirm the deploy short of a visitor.

Fix

Docs only. No CLI or behaviour change: a configured url is already sent with every manifest push, whatever the environment label.

Verified

  • npm test: 239 files, 4,084 tests pass.
  • npm run capabilities:check: up to date, no vocabulary change.

Release order: the guide says Patchstack applies the address over "a placeholder or a builder preview". The preview half depends on patchstack/saas#1953, so release Connect with this text only after that is deployed.

Outstanding: the hostile field test (node field-test/run.mjs --persona hostile --rounds 3), plus standard for doc accuracy, must run right after the release that carries this. The fixture installs the published tarball.

Out of scope, worth a follow-up

guide could print this step when a production build reports no address. That's a CLI change, so it deserves its own PR.

Docs: not needed. The public docs change for the server side is patchstack/documentation#105.

🤖 Generated with Claude Code

Patchstack confirms a deploy by reading the build marker off the live
page: from a visitor's widget, or from its own scheduled check of the
site's address. A new site may have no visitors for days, so the
scheduled check is often the only confirmation, and it needs an address.
Only a few hosts report their production address themselves.

The deploy guide now has the agent put the public address in
.patchstackrc.json as "url" and run one scan, on every other host.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@mariojgt

mariojgt commented Oct 1, 2026

Copy link
Copy Markdown
Contributor Author

/review

@coderbuds

coderbuds Bot commented Oct 1, 2026

Copy link
Copy Markdown

Clear documentation addition detailing how to specify a live site address.

🎯 Quality: 97% Elite · 📦 Size: Tiny

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

See how your team is trending →

@mariojgt
mariojgt merged commit a01645e into main Oct 1, 2026
18 checks passed
@mariojgt
mariojgt deleted the docs/confirm-deploy-without-heartbeat branch October 1, 2026 10:07
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