@sellable/install 0.1.12 → 0.1.14

package/bin/sellable-install.mjs

@@ -15,8 +15,15 @@ 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.12";
-const CODEX_PLUGIN_COMPAT_VERSIONS = ["0.1.8", "0.1.9", "0.1.10", "0.1.11"];
+const CODEX_PLUGIN_VERSION = "0.1.14";
+const CODEX_PLUGIN_COMPAT_VERSIONS = [
+  "0.1.8",
+  "0.1.9",
+  "0.1.10",
+  "0.1.11",
+  "0.1.12",
+  "0.1.13",
+];
 const INSTALL_PACKAGE_SPEC = `@sellable/install@${CODEX_PLUGIN_VERSION}`;
 
 function usage() {
@@ -460,9 +467,9 @@ instruction loading, file lookup, plugin cache versions, missing linked files,
 or tool discovery. Start in product language:
 
 \`\`\`text
-I’ll build this as an approval-gated Sellable campaign. First I’ll confirm who
-we’re launching for, then I’ll use the quick question panel to collect the
-campaign choices before anything is created.
+I’ll build this as an approval-gated Sellable campaign. First I’ll ask who you
+are, use your LinkedIn or company site to understand the company, then confirm
+the sender before anything is created.
 \`\`\`
 
 If a linked/local skill file is stale or missing, silently use the installed
@@ -536,54 +543,89 @@ sender name in the invocation, do one lightweight lookup first:
 Then summarize what you found in one or two lines and ask the user to confirm
 the campaign subject and sender before continuing.
 
-If the user did not provide the launch identity, make the first quick question
-panel an identity gate. The point of this gate is not "pick a sender"; it is to
-learn who the user is / what company we are launching for, and who we should
-send from. Before that gate, call \`mcp__sellable__list_senders\` once if it is
-available, only so you can offer connected senders as shortcuts.
+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:
+
+\`\`\`text
+I’m ready to build this in {workspace}. I found {matched sender} connected here.
+
+Is that you, and is this campaign for {company}?
+\`\`\`
 
-The customer-facing shape should be:
+The options must be:
+
+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 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
+\`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.
+
+If there is no strong sender match, make the first quick question panel 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:
 
 \`\`\`text
-I found these connected senders in {workspace}: {sender names}.
+I’m ready to build this in {workspace}.
 
-First I need to know who this campaign is for and who we’re sending from. If
-one of these connected senders is you, pick them; otherwise paste your LinkedIn
-URL or company website.
+First, what’s your LinkedIn URL? If you’d rather start from the company, paste
+the company website instead.
 \`\`\`
 
-The identity gate should ask:
+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\`.
 
-1. \`Who is this campaign for?\` Options: connected sender names if available,
-   \`I’ll paste a LinkedIn profile\`, \`I’ll paste a company website/domain\`,
-   \`Other / custom\`.
-2. \`Who should the LinkedIn messages send from?\` Options: \`same person/company\`,
-   connected sender names if available, \`I’ll paste a different sender profile\`,
-   \`Other / custom\`.
+After that answer, 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.
 
-After that answer, do the lightweight lookup. For a connected sender, call
-\`mcp__sellable__enrich_sender\` and identify their current or most recent
-company. For a LinkedIn profile, call
-\`mcp__sellable__fetch_linkedin_profile\` and infer the current or most recent
-company from the profile. Then ask:
+If \`mcp__sellable__list_senders\` did not already run, call it once after the
+lookup to see whether the fetched user appears to match a connected sender. If
+there is a likely match, ask:
 
 \`\`\`text
-Cool — I have this as {campaign subject/company}, sending from {sender}. Is that right?
+Cool — are you {matched sender}, and is this campaign for {company}?
 \`\`\`
 
-After the user confirms the subject and sender, run one lightweight company lookup
-(\`mcp__sellable__fetch_company\` when possible, otherwise one web lookup), then
-ask the campaign setup questions. The setup questions should use the confirmed
-company context so they do not feel generic.
+If there is no likely sender match, ask:
+
+\`\`\`text
+Cool — I have this campaign as {company}. Who should the LinkedIn messages send from?
+\`\`\`
+
+Sender options should include connected sender names if available, \`same as
+me\`, \`I’ll paste a different sender profile\`, and \`Other / custom\`.
+
+After the user confirms the subject and sender, run one lightweight company
+lookup if it has not already run, then ask the campaign setup questions. The
+setup questions should use the confirmed company context so they do not feel
+generic.
 
 Before the identity gate, use this customer-facing shape:
 
 \`\`\`text
 I’m ready to build the campaign in {workspace}.
 
-First I need to confirm who this campaign is for and who we’re sending from. If
-you already have a connected sender, I can use that to infer the company;
-otherwise paste a LinkedIn profile or company website and I’ll look it up.
+First I’ll check whether your Sellable token already tells me who you are. If
+not, I’ll ask for your LinkedIn URL or company website, look it up, then confirm
+the company and sender before we pick the target, offer, proof, and lead source.
 
 Then I’ll turn that into a campaign brief for you to approve before anything is created.
 \`\`\`

package/package.json

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