@sellable/install 0.1.25 → 0.1.26

package/bin/sellable-install.mjs

@@ -15,7 +15,7 @@ import { createInterface } from "node:readline/promises";
 const DEFAULT_API_URL = "https://app.sellable.dev";
 const DEFAULT_SERVER_PACKAGE =
   process.env.SELLABLE_MCP_PACKAGE || "@sellable/mcp";
-const CODEX_PLUGIN_VERSION = "0.1.25";
+const CODEX_PLUGIN_VERSION = "0.1.26";
 const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.8",
   "0.1.9",
@@ -34,6 +34,7 @@ const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.22",
   "0.1.23",
   "0.1.24",
+  "0.1.25",
 ];
 const INSTALL_PACKAGE_SPEC = `@sellable/install@${CODEX_PLUGIN_VERSION}`;
 
@@ -541,6 +542,11 @@ Use the host-native structured question gate for intake and approval:
   installer enables this in Default mode with
   \`[features].default_mode_request_user_input = true\`.
 
+Use the structured question gate only for multiple-choice decisions or approval
+gates. Never use it to collect open text input like LinkedIn URLs, company
+domains, notes, pasted context, campaign ideas, or feedback. For open text, ask
+in normal chat and wait for the user to paste the value.
+
 Customer-facing language must call this "a couple setup choices" during normal
 campaign progress. Use "quick question panel" only when explaining a missing
 Codex/Claude setup capability. Do not tell customers about \`request_user_input\`,
@@ -577,9 +583,10 @@ the campaign subject and sender before continuing.
 If the user did not provide the launch identity, quietly call
 \`mcp__sellable__list_senders\` once if available. This is a shortcut to deduce
 who the user might be from their Sellable API token and connected LinkedIn
-accounts. Do not present it as a sender picker yet. If there is one strong
-likely sender, use \`mcp__sellable__enrich_sender\` to infer their current or
-most recent company, then ask a structured confirmation question:
+accounts. Do not ask the user to pick an input type before checking connected
+senders. If there is any likely connected sender, use
+\`mcp__sellable__enrich_sender\` on the best match to infer their current or most
+recent company, then ask a structured confirmation question:
 
 \`\`\`text
 I’m ready to build this in {workspace}. I found {matched sender} connected here.
@@ -587,26 +594,30 @@ I’m ready to build this in {workspace}. I found {matched sender} connected her
 Is that you, and is this campaign for {company}?
 \`\`\`
 
-The options must be:
+The structured options must be no more than three choices:
+
+1. \`Yes — use {matched sender} for {company}\`
+2. \`No — I'll paste a LinkedIn profile\`
+3. \`Use a company domain instead\`
 
-1. \`Yes, that's me and this is for {company}\`
-2. \`That's me, but this is for a different company\`
-3. \`No, I'll paste my LinkedIn URL so you can look me up\`
-4. \`No, I'll paste the company website instead\`
-5. \`Other / custom\`
+If there are multiple likely connected senders, mention the best one in the
+question and use option 2 for either a different connected sender or a pasted
+LinkedIn profile.
 
-If the user chooses option 2, ask for the company website/domain and call
-\`mcp__sellable__fetch_company\` when possible, otherwise one web lookup. If the
-user chooses option 3, ask for their LinkedIn URL, call
+Use the structured question tool only for the choice. Do not use
+\`request_user_input\`/\`AskUserQuestion\` to collect a LinkedIn URL, company
+domain, or freeform text. If the user chooses option 2, ask in normal chat:
+\`Paste the LinkedIn URL I should use, and I’ll look it up.\` Then call
 \`mcp__sellable__fetch_linkedin_profile\`, infer their current or most recent
-company, then confirm company and sender again. If the user chooses option 4,
-ask for the company website/domain, call \`mcp__sellable__fetch_company\` when
-possible, otherwise one web lookup, then ask who the LinkedIn messages should
-send from.
+company, and confirm company and sender again. If the user chooses option 3, ask
+in normal chat: \`Paste the company domain, and I’ll do a quick lookup before we
+keep going.\` Then call \`mcp__sellable__fetch_company\` when possible, otherwise
+one web lookup, and ask who the LinkedIn messages should send from.
 
 If \`mcp__sellable__list_senders\` returns zero connected senders, avoid the
-sender-confirmation branch entirely. Ask for the user's LinkedIn URL or the
-company they want to send on behalf of so you can research context:
+sender-confirmation branch entirely. Do not ask the user to choose an input type
+with the structured question tool. Ask in normal chat for the user's LinkedIn
+URL or the company they want to send on behalf of so you can research context:
 
 \`\`\`text
 I’m ready to build this in {workspace}.
@@ -616,11 +627,11 @@ behalf of. I’ll use that to understand the company before we pick the target,
 offer, proof, and lead source.
 \`\`\`
 
-If there is no strong sender match, make the first setup choice ask for the
-user's LinkedIn URL or company website. The point of this gate is not "pick a
-sender"; it is to learn who the user is, infer the current or most recent
-company, and then confirm who we are sending from. The customer-facing shape
-should be:
+If there is no strong sender match, do not show a structured choice that says
+"LinkedIn profile" vs "Company website". The point of this gate is not "pick a
+sender" or "pick an input type"; it is to learn who the user is, infer the
+current or most recent company, and then confirm who we are sending from. The
+customer-facing shape should be:
 
 \`\`\`text
 I’m ready to build this in {workspace}.
@@ -629,12 +640,7 @@ First, what’s your LinkedIn URL? If you’d rather start from the company, pas
 the company website instead.
 \`\`\`
 
-The LinkedIn/company identity gate should ask:
-
-1. \`What’s your LinkedIn URL?\` Options: \`I’ll paste my LinkedIn profile\`,
-   \`I’ll paste the company website instead\`, \`Other / custom\`.
-
-After that answer, do the lightweight lookup. For a LinkedIn profile, call
+After the user pastes a URL/domain, do the lightweight lookup. For a LinkedIn profile, call
 \`mcp__sellable__fetch_linkedin_profile\` and infer the user's current or most
 recent company from the profile. For a company website, call
 \`mcp__sellable__fetch_company\` when possible, otherwise one web lookup.
@@ -904,10 +910,10 @@ brief before anything is created.
 Good identity setup:
 
 \`\`\`text
-I’ll check whether you already have a connected LinkedIn account here. If I can’t
-confirm it, I’ll ask for your LinkedIn URL or company website and use that to
-understand the company before we choose the target, offer, proof, and lead
-source.
+I’ll check whether you already have a connected sender here. If I find one, I’ll
+ask whether that’s you and whether this campaign is for that company. If not,
+just paste your LinkedIn URL or company domain and I’ll look it up before we
+keep going.
 \`\`\`
 
 Bad:
@@ -919,9 +925,15 @@ First I’ll check whether your Sellable token already tells me who you are.
 Better:
 
 \`\`\`text
-I’ll first check whether you already have a connected sender here. If not, I’ll
-ask for your LinkedIn URL or company website and use that to understand the
-campaign before we choose the audience and offer.
+I found Christian Reyes connected here. Is that you, and is this campaign for
+Sellable? If not, choose LinkedIn profile or company domain and I’ll ask you to
+paste it in chat.
+\`\`\`
+
+Bad:
+
+\`\`\`text
+What should I use to confirm who this campaign is for?
 \`\`\`
 
 Bad:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.25",
+  "version": "0.1.26",
   "type": "module",
   "description": "One-command installer for Sellable MCP in Claude Code and Codex",
   "bin": {