@sellable/install 0.1.13 → 0.1.14
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bin/sellable-install.mjs +20 -4
- package/package.json +1 -1
package/bin/sellable-install.mjs
CHANGED
|
@@ -15,13 +15,14 @@ import { createInterface } from "node:readline/promises";
|
|
|
15
15
|
const DEFAULT_API_URL = "https://app.sellable.dev";
|
|
16
16
|
const DEFAULT_SERVER_PACKAGE =
|
|
17
17
|
process.env.SELLABLE_MCP_PACKAGE || "@sellable/mcp";
|
|
18
|
-
const CODEX_PLUGIN_VERSION = "0.1.
|
|
18
|
+
const CODEX_PLUGIN_VERSION = "0.1.14";
|
|
19
19
|
const CODEX_PLUGIN_COMPAT_VERSIONS = [
|
|
20
20
|
"0.1.8",
|
|
21
21
|
"0.1.9",
|
|
22
22
|
"0.1.10",
|
|
23
23
|
"0.1.11",
|
|
24
24
|
"0.1.12",
|
|
25
|
+
"0.1.13",
|
|
25
26
|
];
|
|
26
27
|
const INSTALL_PACKAGE_SPEC = `@sellable/install@${CODEX_PLUGIN_VERSION}`;
|
|
27
28
|
|
|
@@ -547,9 +548,7 @@ If the user did not provide the launch identity, quietly call
|
|
|
547
548
|
who the user might be from their Sellable API token and connected LinkedIn
|
|
548
549
|
accounts. Do not present it as a sender picker yet. If there is one strong
|
|
549
550
|
likely sender, use \`mcp__sellable__enrich_sender\` to infer their current or
|
|
550
|
-
most recent company, then ask:
|
|
551
|
-
|
|
552
|
-
The customer-facing shape should be:
|
|
551
|
+
most recent company, then ask a structured confirmation question:
|
|
553
552
|
|
|
554
553
|
\`\`\`text
|
|
555
554
|
I’m ready to build this in {workspace}. I found {matched sender} connected here.
|
|
@@ -557,6 +556,23 @@ I’m ready to build this in {workspace}. I found {matched sender} connected her
|
|
|
557
556
|
Is that you, and is this campaign for {company}?
|
|
558
557
|
\`\`\`
|
|
559
558
|
|
|
559
|
+
The options must be:
|
|
560
|
+
|
|
561
|
+
1. \`Yes, that's me and this is for {company}\`
|
|
562
|
+
2. \`That's me, but this is for a different company\`
|
|
563
|
+
3. \`No, I'll paste my LinkedIn URL so you can look me up\`
|
|
564
|
+
4. \`No, I'll paste the company website instead\`
|
|
565
|
+
5. \`Other / custom\`
|
|
566
|
+
|
|
567
|
+
If the user chooses option 2, ask for the company website/domain and call
|
|
568
|
+
\`mcp__sellable__fetch_company\` when possible, otherwise one web lookup. If the
|
|
569
|
+
user chooses option 3, ask for their LinkedIn URL, call
|
|
570
|
+
\`mcp__sellable__fetch_linkedin_profile\`, infer their current or most recent
|
|
571
|
+
company, then confirm company and sender again. If the user chooses option 4,
|
|
572
|
+
ask for the company website/domain, call \`mcp__sellable__fetch_company\` when
|
|
573
|
+
possible, otherwise one web lookup, then ask who the LinkedIn messages should
|
|
574
|
+
send from.
|
|
575
|
+
|
|
560
576
|
If there is no strong sender match, make the first quick question panel ask for
|
|
561
577
|
the user's LinkedIn URL or company website. The point of this gate is not "pick
|
|
562
578
|
a sender"; it is to learn who the user is, infer the current or most recent
|