setup

Pincushion Setup

Connect this project to Pincushion so teammates and clients can pin feedback on its pages from the Pincushion app and your agent can read those pins, and compile a critique-context brief grounded in the actual page sources sitting in this repo. If the owner already created the project in the app (https://www.pincushion.io/app), pass its projectId to configure_project instead of creating a new one. The Pincushion AI critic reads this brief on every pin.

Run this once per project. You'll need:

• A project name
• The local URL where you develop (e.g. localhost:3000)
• The live/staging URL — optional but recommended. Ask for it; never guess it from the package name
• A choice of comment access mode (Pro/Team only — Free is always "open")

Steps

1. Ask the user (don't assume) which comment-access mode they want:

   • Open — anyone with the review link can comment. Best for indie projects, public betas, pre-launch demos. Free, Pro, Team.
   • Domain-restricted — only emails matching a list of domains. Requires Pro or Team.
   • Invite-only — only emails the owner explicitly adds. Requires Pro or Team.

   Separately ask: “May I inspect locally detected deployment candidates and, only after you choose one and explicitly approve, begin optional deployment automation?” Only explicit owner consent authorizes the optional deploymentAutomation: "auto" field below; otherwise omit it.

2. Call configure_project:

configure_project({
  name: "<project name>",
  urls: ["localhost:3000", "myapp.vercel.app"],
  commentAccess: "open" | "domain" | "invited",
  allowedDomains: ["acme.com"]   // only if commentAccess: "domain"
})

Save the returned projectId for step 4.

If local detection finds multiple candidates, ask the owner to select deploymentProvider; do not call a provider while it is ambiguous. If the owner explicitly authorized automation, add deploymentAutomation: "auto" (and the selected provider when needed) to that call. A successful response confirms provider read-back only; the first accepted production receipt is still pending. Unsupported provider APIs require the returned redacted manual setup handoff. Use get_deployment_reconciliation_status for independent reconciliation, fresh desktop/mobile frames, queue, and external Crit evidence. Do not modify source or CI without owner approval.