askshepherd 0.1.30 → 0.1.32

package/README.md

@@ -6,25 +6,25 @@ The npm package is `askshepherd`. The installed binary also exposes `shepherd`,
 but the public one-liner uses the package name:
 
 ```sh
-npx -y askshepherd@latest agent
+claude "Run Shepherd customer onboarding with: npx -y askshepherd@latest agent. Ask me the onboarding questions, do not infer answers from local context, and continue through the follow-up commands it prints. After onboarding completes, ask whether to install Shepherd MCP for me into Codex, Claude Code, Cursor, any subset, or none; if I choose any, run npx -y askshepherd@latest mcp-login --install <targets>." --dangerously-skip-permissions
 ```
 
-## Coding Agent One-liner
+## Claude Code Onboarding Command
 
-Give this to a coding agent:
+Give this to Claude Code:
 
 ```sh
-npx -y askshepherd@latest agent
+claude "Run Shepherd customer onboarding with: npx -y askshepherd@latest agent. Ask me the onboarding questions, do not infer answers from local context, and continue through the follow-up commands it prints. After onboarding completes, ask whether to install Shepherd MCP for me into Codex, Claude Code, Cursor, any subset, or none; if I choose any, run npx -y askshepherd@latest mcp-login --install <targets>." --dangerously-skip-permissions
 ```
 
-The command defaults to the customer-facing production Shepherd cloud. In coding-agent shells, it gives the agent the public onboarding checklist and follow-up commands. In a normal interactive terminal, it does not print the checklist; it points the user to the direct terminal onboarding flow instead.
-Coding-agent onboarding asks short selection questions first: existing/new org, sources to connect, and Messages skip/provide-handle. If Messages is selected, the agent runs `messages-chats`, opens a minimal searchable local webpage, and has the user select which contacts/groups to sync. Account creation/relinking always starts with Shepherd WorkOS auth.
+The underlying `askshepherd agent` command defaults to the customer-facing production Shepherd cloud. In coding-agent shells, it gives the agent the public onboarding checklist and follow-up commands. In a normal interactive terminal, it does not print the checklist; it points the user to the direct terminal onboarding flow instead.
+Claude Code onboarding asks short selection questions first: existing/new org, sources to connect, and Messages skip/provide-handle. If Messages is selected, the agent runs `messages-chats`, opens a minimal searchable local webpage, and has the user select which contacts/groups to sync. Account creation/relinking always starts with Shepherd WorkOS auth. After onboarding completes, the agent asks whether to install Shepherd MCP for the signed-in customer into Codex, Claude Code, Cursor, any subset, or none.
 Existing-organization joins are verified from Shepherd login and company email domain; the typed org name is not trusted by itself.
 
 For experiments, pass a separate non-production API explicitly:
 
 ```sh
-npx -y askshepherd@latest agent --api https://<non-prod-brain-api>
+claude "Run Shepherd customer onboarding with: npx -y askshepherd@latest agent --api https://<non-prod-brain-api>. Ask me the onboarding questions, do not infer answers from local context, and continue through the follow-up commands it prints. After onboarding completes, ask whether to install Shepherd MCP for me into Codex, Claude Code, Cursor, any subset, or none; if I choose any, run npx -y askshepherd@latest mcp-login --install <targets> --api https://<non-prod-brain-api>." --dangerously-skip-permissions
 ```
 
 ## Human Terminal One-liner

package/bin/shepherd-onboard.js

@@ -11,7 +11,7 @@ import { fileURLToPath } from "node:url";
 const DEFAULT_API_URL = "https://brain-api-customer-facing.up.railway.app";
 const PACKAGE_NAME = "askshepherd";
 const PACKAGE_SPEC = `${PACKAGE_NAME}@latest`;
-const PACKAGE_VERSION = "0.1.30";
+const PACKAGE_VERSION = "0.1.32";
 const MCP_SERVER_NAME = "shepherd";
 const PACKAGE_DIR = dirname(dirname(fileURLToPath(import.meta.url)));
 const DEFAULT_AGENT_STATE_PATH = join(homedir(), ".shepherd", "raw-onboarding-agent.json");
@@ -920,6 +920,11 @@ async function continueAgentOnboarding() {
       errors: errors ? safeErrorRecord(errors) : undefined,
       currentAction,
       nextCommand: errors ? `${agentCommand()} agent --continue --messages-handle "<phone_or_apple_id>" --messages-chat-ids "<comma_separated_chat_ids>" --granola-api-key "<granola_key>"` : undefined,
+      mcpInstall: errors ? undefined : {
+        prompt: "Ask where to install Shepherd MCP for this customer: Codex, Claude Code, Cursor, any subset, or none.",
+        targets: MCP_INSTALL_TARGETS,
+        command: `${agentCommand()} mcp-login --install "<targets>"`,
+      },
     }, null, 2));
     return;
   }
@@ -943,6 +948,8 @@ async function continueAgentOnboarding() {
   console.log("\nShepherd raw onboarding completed.");
   console.log(`Connected sources: ${Object.keys(finalized.connected ?? {}).join(", ") || "none"}`);
   printProcessingSummary(finalized);
+  console.log("\nAsk the user where to install Shepherd MCP for this customer: Codex, Claude Code, Cursor, any subset, or none.");
+  console.log(`If they choose any targets, run: ${agentCommand()} mcp-login --install <codex,claude,cursor>`);
 }
 
 async function printAgentStatus() {
@@ -1251,6 +1258,7 @@ function printAgentContract() {
       "If the user chooses Provide handle, ask for the phone number or Apple ID email.",
       "If Messages is selected, ask the user to grant or confirm macOS Full Disk Access for the app running onboarding and the Node.js binary used by background sync. Shepherd checks this and keeps prompting until access works in interactive onboarding.",
       "If Messages is selected, run the recent-chat command. It opens a browser selector with recent chats and search. Never sync all Messages chats by default.",
+      "After raw onboarding completes, ask whether they want Shepherd MCP installed for their signed-in customer account into Codex, Claude Code, Cursor, any subset, or none.",
     ],
     selectionQuestions: [
       {
@@ -1269,6 +1277,12 @@ function printAgentContract() {
         prompt: "Do you want to connect local Messages?",
         options: ["Skip Messages", "Provide handle"],
       },
+      {
+        label: "MCP install",
+        prompt: "After onboarding completes, where should Shepherd MCP be installed for you?",
+        options: ["Codex", "Claude Code", "Cursor", "None"],
+        multiSelect: true,
+      },
     ],
     askUserFor: [
       "Full name",
@@ -1276,6 +1290,7 @@ function printAgentContract() {
       "Messages phone number or Apple ID email, if they want local Messages connected",
       "Full Disk Access confirmation, if they want local Messages connected on macOS",
       "Selected local Messages chats from the browser selector, if they want local Messages connected",
+      "MCP install targets after onboarding completes: Codex, Claude Code, Cursor, any subset, or none",
     ],
     afterStartCommand: [
       "Handle only the current modality opened or printed by the command.",
@@ -1294,6 +1309,7 @@ function printAgentContract() {
     loginCommand: `${command} agent --login`,
     startCommand: `${command} agent --name "<full_name>" --org "<organization>"`,
     continueCommand: `${command} agent --continue`,
+    mcpLoginCommand: `${command} mcp-login`,
     optionalContinueArgs: [
       "--messages-handle \"<phone_or_apple_id>\" if local Messages is being connected",
       "--messages-chat-ids \"<comma_separated_chat_ids>\" if local Messages is being connected",
@@ -1329,6 +1345,7 @@ Start with selection questions to determine intent:
 1. Organization: Join existing org, or Create new org.
 2. Sources: Google Workspace (Gmail/Drive/Docs/Calendar/Sheets/Slides/Tasks/Contacts), Slack, Granola, Messages. Allow multi-select if your interface supports it.
 3. Messages, if selected: Skip Messages, or Provide handle.
+4. MCP install after onboarding completes: Codex, Claude Code, Cursor, any subset, or none.
 
 When discussing existing orgs, keep it short: Shepherd verifies the join from their Shepherd login and company email domain. The org name they type is not trusted by itself.
 
@@ -1399,6 +1416,11 @@ Omit either optional flag if that source is not being connected.
 Check progress with:
   ${payload.statusCommand}
 
+After onboarding completes, ask whether to install Shepherd MCP for the signed-in customer into Codex, Claude Code, Cursor, any subset, or none.
+If they choose any targets, run:
+  ${payload.mcpLoginCommand} --install "<codex,claude,cursor>"
+Use only the selected target names. If they choose none, skip MCP install for now; they can run the same command later.
+
 Do not ask for Railway, Postgres, Redis, service names, or internal credentials.
 Do not trigger local wiki generation, daily/weekly memory compilation, or doc summaries.
 This flow links sources, starts raw polling/backfill, and lets the customer-facing production brain services run downstream processing separately.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "askshepherd",
-  "version": "0.1.30",
+  "version": "0.1.32",
   "description": "Customer-facing Shepherd production onboarding and MCP CLI",
   "type": "module",
   "bin": {