@sellable/install 0.1.11 → 0.1.12

package/bin/sellable-install.mjs

@@ -15,8 +15,8 @@ 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.11";
-const CODEX_PLUGIN_COMPAT_VERSIONS = ["0.1.8", "0.1.9", "0.1.10"];
+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 INSTALL_PACKAGE_SPEC = `@sellable/install@${CODEX_PLUGIN_VERSION}`;
 
 function usage() {
@@ -519,8 +519,10 @@ loading, or skill file versions.
 
 Do not treat the active Sellable workspace as the campaign subject. The
 workspace only tells you where the campaign will be saved. Before buyer, CTA,
-proof, or source questions, identify and confirm who the campaign is launching
-for.
+proof, or source questions, identify two things:
+
+1. who/what company this campaign is for, and
+2. who the LinkedIn messages should send from.
 
 If the user supplied a LinkedIn profile, website, domain, company name, or
 sender name in the invocation, do one lightweight lookup first:
@@ -532,28 +534,56 @@ sender name in the invocation, do one lightweight lookup first:
   \`mcp__sellable__enrich_sender\`.
 
 Then summarize what you found in one or two lines and ask the user to confirm
-the launch identity before continuing.
+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. Ask who we are launching for, with options like:
+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.
+
+The customer-facing shape should be:
+
+\`\`\`text
+I found these connected senders in {workspace}: {sender names}.
+
+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.
+\`\`\`
 
-1. Use one of my connected Sellable senders
-2. I’ll paste a LinkedIn profile
-3. I’ll paste a company website/domain
-4. Other / custom
+The identity gate should ask:
+
+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 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:
+
+\`\`\`text
+Cool — I have this as {campaign subject/company}, sending from {sender}. Is that right?
+\`\`\`
 
-After that answer, do the lightweight lookup, confirm the company/sender
-context, then ask the campaign setup questions. The setup questions should use
-the confirmed company context so they do not feel generic.
+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.
 
 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 we’re launching for. If you give me a LinkedIn
-profile or company website, I’ll use that to understand the company, then I’ll
-confirm it with you before we pick the target, offer, proof, and lead source.
+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.
 
 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.11",
+  "version": "0.1.12",
   "type": "module",
   "description": "One-command installer for Sellable MCP in Claude Code and Codex",
   "bin": {