askshepherd 0.1.38 → 0.1.39

package/README.md

@@ -75,7 +75,8 @@ above; it performs the bounded local checks.
 
 ## Set Up Coding Agent Sessions
 
-Use this when the user asks "Help me set up coding agent sessions":
+Use this when the user asks "Help me set up coding agent sessions" or "Enable
+coding agent sessions locally for Shepherd":
 
 ```sh
 npx -y askshepherd@latest agent --login
@@ -120,9 +121,10 @@ The saved MCP state includes:
 The installed MCP server is local npm first, remote brain second. For questions
 like "what do I have set up on Shepherd?", "is Shepherd syncing?", or "help me
 set up coding agent sessions", the MCP exposes local tools such as
-`shepherd_status` and `shepherd_setup_coding_sessions` that route agents to the
-local `askshepherd status` / add-source flow. Production memory and wiki tools
-remain remote Railway-backed tools for source recall and company-memory answers.
+`shepherd_status`, `shepherd_setup_coding_sessions`, and
+`shepherd_enable_coding_sessions` that route agents to the local
+`askshepherd status` / add-source flow. Production memory and wiki tools remain
+remote Railway-backed tools for source recall and company-memory answers.
 Those local MCP tools are also the permission boundary: an MCP client should not
 use shell or file tools to inspect the user's folders or repositories for setup.
 

package/bin/shepherd-onboard.js

@@ -822,13 +822,20 @@ function localMcpTools() {
       annotations: readOnlyAnnotations,
       _meta: { provider: "local_npm", command: `${agentCommand()} agent --add-sources coding-sessions` },
     },
+    {
+      name: "shepherd_enable_coding_sessions",
+      description: "Alias for shepherd_setup_coding_sessions. Use when the user asks to enable coding agent sessions locally for Shepherd. Return the local askshepherd npm setup commands; do not search, list, or read the user's folders or repos.",
+      inputSchema: emptyInputSchema,
+      annotations: readOnlyAnnotations,
+      _meta: { provider: "local_npm", command: `${agentCommand()} agent --add-sources coding-sessions` },
+    },
   ];
 }
 
 function localMcpInstructions(remoteInstructions, remoteConnectError) {
   return [
     "This MCP server is the local askshepherd npm wrapper plus production Shepherd memory/wiki tools.",
-    `For local setup/sync questions like "what do I have set up on Shepherd", "what have I enabled", "is Shepherd syncing", "help me set up coding agent sessions", or "enable coding sessions", use shepherd_status or shepherd_setup_coding_sessions first. These local tools route to the local askshepherd npm status/setup flow. The askshepherd CLI is the only component that may perform bounded local checks of Shepherd state, LaunchAgents, and known Codex/Claude session locations.`,
+    `For local setup/sync questions like "what do I have set up on Shepherd", "what have I enabled", "is Shepherd syncing", "help me set up coding agent sessions", "enable coding sessions", or "enable coding agent sessions locally for Shepherd", use shepherd_status, shepherd_setup_coding_sessions, or shepherd_enable_coding_sessions first. These local tools route to the local askshepherd npm status/setup flow. The askshepherd CLI is the only component that may perform bounded local checks of Shepherd state, LaunchAgents, and known Codex/Claude session locations.`,
     "Hard boundary: do not use shell or filesystem tools such as ls, find, rg, grep, cat, Read, Glob, or Explore to inspect the user's home directory, repositories, ~/.codex, ~/.claude, or ~/.shepherd for Shepherd setup. If local status is needed, call shepherd_status or run the exact askshepherd status command.",
     `If the user asks for raw local status outside MCP, tell them to run ${agentCommand()} status. For setup of coding agent sessions, ask consent, then use ${agentCommand()} agent --login if needed, ${agentCommand()} agent --add-sources coding-sessions --name "<full_name>" --org "<organization>", ${agentCommand()} agent --continue, then ${agentCommand()} status.`,
     "Use production memory/wiki tools only for company-memory questions, source recall, wiki lookup, messages/meetings retrieval, or coding-session work history that has already synced to Shepherd.",
@@ -849,7 +856,7 @@ async function callLocalMcpTool(name) {
     ].join("\n\n"));
   }
 
-  if (name === "shepherd_setup_coding_sessions") {
+  if (name === "shepherd_setup_coding_sessions" || name === "shepherd_enable_coding_sessions") {
     const status = await collectShepherdStatus();
     return localMcpTextResult(renderCodingSessionsSetupMcpResult(status));
   }

package/package.json

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