create-snipara 2.0.5 → 2.0.7

package/README.md

@@ -12,8 +12,8 @@ npx create-snipara
 
 `create-snipara` is the simple onboarding package for the agent path. It
 creates or reuses auth, writes Hosted MCP config, and prepares the local project
-so an LLM client can use Snipara context and reviewed memory. Install once with
-`create-snipara`; continue every session with `snipara-companion`.
+so an LLM client can use Snipara context and reviewed memory. The default path is
+hosted-only so the first success is a grounded answer, not a local tooling tour.
 
 Use it when the goal is outcome-first agent work: the user asks for judgment,
 implementation, release, or verification, and the agent handles Snipara context,
@@ -54,7 +54,7 @@ The product surfaces remain:
 - Hosted MCP for LLM agents, context, and reviewed memory
 - HTTP API / SDK for apps, integrators, backends, and pipelines
 
-The default CLI path wires the local companion around those surfaces:
+Advanced flags can wire local helpers around those surfaces:
 
 - `snipara-companion` for Git-style status, briefs, timelines, phase commits,
   handoffs, resume, and local workflow commands
@@ -69,12 +69,12 @@ The CLI now works around explicit install profiles:
 
 | Profile            | What it installs                              | Best for                                                                                                            |
 | ------------------ | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
-| `hosted-companion` | MCP + `snipara-companion`                     | Default: hosted context plus managed local workflow                                                                 |
-| `hosted-only`      | Hosted MCP config only                        | Locked-down or minimal environments                                                                                 |
+| `hosted-only`      | Hosted MCP config only                        | Default: first grounded answer with no local companion, hooks, or sandbox                                           |
+| `hosted-companion` | MCP + `snipara-companion`                     | Hosted context plus managed local workflow after first value                                                        |
 | `full-stack`       | MCP + `snipara-companion` + `snipara-sandbox` | Hosted context plus sandboxed local execution. Does not include orchestrator unless `--with-orchestrator` is passed |
 | `runtime-only`     | `snipara-sandbox` only                        | Local execution without hosted API                                                                                  |
 
-Default profile: `hosted-companion`
+Default profile: `hosted-only`
 
 ## Free Account Fit
 
@@ -107,10 +107,10 @@ That distinction matters:
 - opens the browser device-flow free Context + Memory account flow when needed
 - writes Hosted MCP configuration
 - detects a GitHub remote and can open the Snipara GitHub App automation path
-- activates the current folder locally through `snipara-companion source init` so docs and code overlay context are available before GitHub approval
+- can activate the current folder locally through `snipara-companion source init` after the user opts into Companion
 - explains the GitHub PR Answer Packs path for AI-assisted pull request workflows
-- installs `snipara-companion` by default for local status, briefs, timelines,
-  phase commits, handoffs, resume, and managed workflows
+- installs `snipara-companion` only with `--advanced`, `--profile hosted-companion`,
+  `--profile full-stack`, or `repair --with-companion`
 - installs optional `snipara-sandbox`
 - installs optional `snipara-orchestrator` for proof gates, drift checks, and htask workflows when requested
 - configures `.mcp.json`
@@ -118,8 +118,8 @@ That distinction matters:
 - creates `AGENTS.md` and `CLAUDE.md` when missing, or appends a marked Snipara section when those files already exist
 - creates `.cursor/rules/snipara.mdc` and `.codex/config.toml` when those files do not already exist
 - validates Codex config against Hosted MCP plus `bearer_token_env_var = "SNIPARA_API_KEY"` and tells users to restart Codex after MCP config changes
-- installs local code overlay Git hooks by default for Claude Code and Codex
-  companion setups, unless `--skip-hooks` is passed
+- installs local code overlay Git hooks only for explicit companion/full-stack
+  setups unless `--skip-hooks` is passed
 - runs a real hosted MCP `tools/list` check and warns if the server still advertises legacy `rlm_*` duplicate tools
 - generates Mistral Le Chat, Mistral Vibe, and LangChain `ChatMistralAI.bindTools` references without embedding secrets
 - writes client-specific companion packs such as `.snipara/companion/CODEX.md` or `.snipara/companion/GEMINI.md`
@@ -155,9 +155,10 @@ The interactive flow now asks for:
 - API key path: existing API key, free signup, or add key later
 - AI client
 
-By default, this uses the recommended `hosted-companion` setup: hosted MCP plus
-the local `snipara-companion` workflow helper. Add `--advanced` when you want profile selection, project id entry,
-hook prompts, GitHub automation prompts, or sandbox provider prompts.
+By default, this uses the minimal `hosted-only` setup: hosted MCP config and a
+doctor report, with no local Companion install, hooks, GitHub approval prompt, or
+sandbox prompt. Add `--advanced` when you want profile selection, project id
+entry, hook prompts, GitHub automation prompts, or sandbox provider prompts.
 Use `--with-orchestrator` only when you explicitly need the advanced production
 validation and htask package; it is not part of `full-stack` by default.
 
@@ -188,11 +189,12 @@ native skills should keep using `AGENTS.md`, `CLAUDE.md`, or project rules as th
 shared instruction surface.
 
 For Codex, `SNIPARA_API_KEY` is the only generated bearer token environment
-variable. If Codex lazily exposes only a minimal Snipara MCP surface after
-restart, force exact discovery for `snipara_recall`, `snipara_context_query`,
-and `snipara_settings`. Use `snipara-companion recall`, `snipara-companion
-query`, and `snipara-companion task-commit` as the reliable local fallback while
-the Codex session reloads or rediscovers tools.
+variable. If Codex exposes only the lean Snipara MCP surface after restart,
+that is expected. Use `snipara_help(query=...)` for routed guidance and
+`snipara_help(list_all=true)` to inspect specialist opt-in surfaces. Use
+`snipara-companion recall`, `snipara-companion query`, and
+`snipara-companion task-commit` as the reliable local fallback when the simple
+hosted tools are not callable.
 
 Existing root `AGENTS.md` and `CLAUDE.md` files are not replaced. The installer
 adds or refreshes a marked Snipara section so project-specific instructions stay
@@ -203,6 +205,12 @@ compaction-safe managed workflow and Git-style agent work commands. Keep the
 machine plan in JSON for stable phase ids; an optional Markdown file can remain
 the human-facing contract.
 
+Enable those local helpers later with:
+
+```bash
+npx create-snipara repair --with-companion
+```
+
 ```bash
 snipara-companion status
 snipara-companion source init .

package/dist/index.js

@@ -13,7 +13,7 @@ import { homedir } from "os";
 // package.json
 var package_default = {
   name: "create-snipara",
-  version: "2.0.5",
+  version: "2.0.7",
   description: "Onboard Snipara Hosted MCP Context + Memory with auth, companion workflows, and optional Snipara Sandbox",
   main: "dist/index.js",
   type: "module",
@@ -197,7 +197,7 @@ function shouldInstallDefaultHooks(aiClient) {
 }
 function buildProgram() {
   const program = new Command();
-  program.name("create-snipara").description("Scaffold hosted Snipara MCP config plus companion workflow helpers").version(VERSION);
+  program.name("create-snipara").description("Scaffold hosted Snipara MCP config; advanced flags add local helpers").version(VERSION);
   program.command("init").description("Install and configure Snipara for this project").option("--api-key <key>", "Snipara API key").option("--slug <slug>", "Project slug").option("--project-id <id>", "Project ID").option(
     "--client <client>",
     "AI client: claude-code, cursor, windsurf, codex, gemini, mistral, chatgpt, vscode, continue, claude-desktop, other"
@@ -543,9 +543,9 @@ function printBanner() {
 \u2551                                                                       \u2551
 \u2551   \u2022 Hosted MCP for LLM agents                                         \u2551
 \u2551   \u2022 Free account path with hosted context and reviewed memory         \u2551
-\u2551   \u2022 Local source activation before GitHub approval                    \u2551
+\u2551   \u2022 First grounded answer before local workflow setup                 \u2551
 \u2551   \u2022 API / SDK for product integrations                                \u2551
-\u2551   \u2022 Optional local companion and Snipara Sandbox helpers              \u2551
+\u2551   \u2022 Optional advanced companion, hooks, and Snipara Sandbox helpers   \u2551
 \u2551   \u2022 One CLI for auth, config, doctor, repair, and upgrade             \u2551
 \u2551                                                                       \u2551
 \u255A\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u255D
@@ -784,7 +784,7 @@ function resolveRequestedProfile(options) {
   if (options.profile && isInstallProfile(options.profile)) {
     return options.profile;
   }
-  return "hosted-companion";
+  return "hosted-only";
 }
 function isInstallProfile(value) {
   return ["hosted-only", "hosted-companion", "full-stack", "runtime-only"].includes(value);
@@ -828,15 +828,15 @@ function normalizeClientOption(value) {
 }
 function installProfileChoices() {
   return [
-    {
-      title: "Hosted + Companion",
-      value: "hosted-companion",
-      description: "Default: hosted MCP config plus managed local workflow commands"
-    },
     {
       title: "Hosted only",
       value: "hosted-only",
-      description: "Minimal setup: hosted MCP config, no local companion or sandbox"
+      description: "Default: hosted MCP config, no local companion, hooks, or sandbox"
+    },
+    {
+      title: "Hosted + Companion",
+      value: "hosted-companion",
+      description: "Add managed local workflow commands after first value"
     },
     {
       title: "Hosted + Companion + Sandbox",
@@ -1492,7 +1492,7 @@ function buildSniparaOnboardingSkill(endpoint, companionPrefix) {
     "",
     `Use the Hosted MCP endpoint: \`${endpoint}\`. Keep the API key in \`SNIPARA_API_KEY\` or the client secret store. Never paste keys into tracked files, prompts, logs, screenshots, or durable memory.`,
     "",
-    "Validate availability with a tool-oriented call such as `snipara_help(list_all=true)`, `snipara_settings`, or a lightweight `snipara_context_query`. Empty MCP resources or resource templates do not prove an outage because Snipara may be exposed as a tool-only MCP server.",
+    'Validate availability with a simple tool-oriented call such as `snipara_help(query="what should I use for project context?")`, `snipara_settings`, or a lightweight `snipara_context_query`. Empty MCP resources or resource templates do not prove an outage because Snipara may be exposed as a tool-only MCP server.',
     "",
     "## Setup Steps",
     "",
@@ -1512,7 +1512,7 @@ function buildSniparaOnboardingSkill(endpoint, companionPrefix) {
     "",
     "## Failure Handling",
     "",
-    "If broad discovery shows only a partial tool surface, call `snipara_help(list_all=true)` before concluding a tool is unavailable. If the client still lags after config changes, use Companion commands as a local fallback for recall, query, and task commit until the MCP session refreshes.",
+    "If broad discovery shows only the lean default tool surface, treat that as normal. Use `snipara_help(query=...)` for routed guidance, `snipara_help(list_all=true)` to inspect specialist opt-in surfaces, and Companion commands as a local fallback for recall, query, and task commit until the MCP session refreshes.",
     ""
   ].join("\n");
 }
@@ -1733,17 +1733,13 @@ This project uses Snipara Hosted MCP for project context and reviewed memory.
 - For Codex, expose the endpoint as a streamable HTTP MCP server and load the
   key from \`SNIPARA_API_KEY\`.
 - At the start of every new thread, validate hosted MCP with a tool-oriented
-  call such as \`snipara_settings\`, \`tools/list\`, or a lightweight
+  call such as \`snipara_settings\`, \`snipara_help(query=...)\`, or a lightweight
   \`snipara_context_query\`. Do not treat empty MCP resources/templates as an
   outage because Snipara may be tool-only.
-- In Codex, if only a minimal Snipara tool subset appears, force precise tool
-  discovery for \`snipara_recall\`, \`snipara_context_query\`, and
-  \`snipara_settings\` before concluding the MCP server is incomplete.
-- If a session appears to expose only a subset of expected Snipara tools, call
-  \`snipara_help(list_all=true)\` and compare exact tool names before concluding
-  that a tool is unavailable. Do not infer absence from one broad discovery
-  pass or a ranked tool-search result.
-- If Codex still exposes only a partial surface after exact discovery, use
+- In Codex, a lean Snipara tool set is expected. Use \`snipara_help(query=...)\`
+  for routed guidance and \`snipara_help(list_all=true)\` to inspect specialist
+  opt-in surfaces before requesting expanded schemas.
+- If Codex still cannot call the simple context or memory tools, use
   \`snipara-companion recall\`, \`snipara-companion query\`, and
   \`snipara-companion task-commit\` as the reliable local fallback, then restart
   or reload Codex after MCP config changes.
@@ -1823,8 +1819,8 @@ Use Snipara Hosted MCP before answering project-specific questions.
 
 - Endpoint: \`${buildHostedMcpEndpoint(answers)}\`
 - Auth: use \`SNIPARA_API_KEY\` from the environment. Never commit keys.
-- At the start of every new thread, validate hosted MCP with a tool-oriented call such as \`snipara_settings\`, \`tools/list\`, or a lightweight \`snipara_context_query\`. Do not treat empty MCP resources/templates as an outage because Snipara may be tool-only.
-- If a session exposes only a subset of expected Snipara tools, call \`snipara_help(list_all=true)\` and compare exact tool names before concluding a tool is unavailable. If only a partial surface remains after exact discovery, use \`snipara-companion recall\`, \`snipara-companion query\`, and \`snipara-companion task-commit\` as a reliable local fallback.
+- At the start of every new thread, validate hosted MCP with a tool-oriented call such as \`snipara_settings\`, \`snipara_help(query=...)\`, or a lightweight \`snipara_context_query\`. Do not treat empty MCP resources/templates as an outage because Snipara may be tool-only.
+- A lean default Snipara tool set is expected. Use \`snipara_help(query=...)\` for routed guidance, \`snipara_help(list_all=true)\` to inspect specialist opt-in surfaces, and \`snipara-companion recall\`, \`snipara-companion query\`, or \`snipara-companion task-commit\` as local fallbacks when the simple tools are unavailable.
 - If the client supports native skills, install the generated Snipara skill pack from \`.snipara/templates/skills\`. Keep \`AGENTS.md\` as the shared fallback for clients without native skill support.
 
 ${EXPERIENCE_GOAL_SECTION}
@@ -1863,8 +1859,8 @@ This workspace uses Snipara Hosted MCP for current project context, business/cli
 
 - Check the configured Snipara MCP server before answering project-specific questions.
 - Endpoint: \`${buildHostedMcpEndpoint(answers)}\`
-- At the start of every new thread, validate hosted MCP with a tool-oriented call such as \`snipara_settings\`, \`tools/list\`, or a lightweight \`snipara_context_query\`. Do not treat empty MCP resources/templates as an outage because Snipara may be tool-only.
-- If a session exposes only a subset of expected Snipara tools, call \`snipara_help(list_all=true)\` and compare exact tool names before concluding a tool is unavailable. If only a partial surface remains after exact discovery, use \`snipara-companion recall\`, \`snipara-companion query\`, and \`snipara-companion task-commit\` as a reliable local fallback.
+- At the start of every new thread, validate hosted MCP with a tool-oriented call such as \`snipara_settings\`, \`snipara_help(query=...)\`, or a lightweight \`snipara_context_query\`. Do not treat empty MCP resources/templates as an outage because Snipara may be tool-only.
+- A lean default Snipara tool set is expected. Use \`snipara_help(query=...)\` for routed guidance, \`snipara_help(list_all=true)\` to inspect specialist opt-in surfaces, and \`snipara-companion recall\`, \`snipara-companion query\`, or \`snipara-companion task-commit\` as local fallbacks when the simple tools are unavailable.
 - If the client supports native skills, install the generated Snipara skill pack from \`.snipara/templates/skills\`. Keep \`AGENTS.md\` as the shared fallback for clients without native skill support.
 
 ${EXPERIENCE_GOAL_SECTION}
@@ -2541,8 +2537,8 @@ function getClientGuidance(client) {
       "Codex should use the hosted MCP surface plus AGENTS.md as the canonical project instruction file.",
       "The generated .snipara/templates/codex-config.toml is a merge-ready snippet for ~/.codex/config.toml if your Codex app does not read project .codex/config.toml.",
       "Use SNIPARA_API_KEY as the only Codex bearer_token_env_var; restart Codex after changing MCP config.",
-      "If Codex lazily exposes only a minimal tool set, force discovery for snipara_recall, snipara_context_query, snipara_settings, and the exact htask or swarm tool names you need; use snipara_help(list_all=true) to confirm the hosted catalog before concluding the MCP surface is incomplete.",
-      "When Codex still exposes only the minimal core tools, use snipara-orchestrator swarm-* and htask-* as the primary path for shared queues and multi-agent task work."
+      "If Codex exposes only the lean Snipara tool set, that is expected. Use snipara_help(query=...) for routed guidance and snipara_help(list_all=true) to inspect specialist opt-in surfaces before requesting exact htask or swarm schemas.",
+      "When Codex cannot expose orchestration schemas directly, use snipara-orchestrator swarm-* and htask-* as the primary path for shared queues and multi-agent task work."
     ];
   }
   if (client === "gemini") {
@@ -2591,6 +2587,26 @@ function getClientGuidance(client) {
 function getCompanionCommands(answers) {
   const projectFlag = answers.projectSlug ? ` --project ${answers.projectSlug}` : "";
   const clientFlag = getCompanionInitClientFlag(answers.aiClient);
+  if (!answers.installCompanion) {
+    const commands = [
+      {
+        title: "Run doctor for this project",
+        command: `${CREATE_SNIPARA_NPX_COMMAND} doctor`,
+        purpose: "Inspect local wiring and hosted MCP reachability after the AI client restarts."
+      },
+      {
+        title: "Enable local companion later",
+        command: `${CREATE_SNIPARA_NPX_COMMAND} repair --with-companion`,
+        purpose: "Opt into local source activation, managed workflows, guards, and task commits after the first hosted answer works."
+      }
+    ];
+    commands.push({
+      title: answers.githubRepo ? "Connect GitHub PR Answer Packs later" : "Connect a GitHub repo for PR Answer Packs",
+      command: `${CREATE_SNIPARA_NPX_COMMAND} --github${answers.githubPath ? ` --github-path ${answers.githubPath}` : ""}`,
+      purpose: "Open the Snipara GitHub App flow only when the user is ready to approve repository access."
+    });
+    return commands;
+  }
   const localSourceCommands = answers.installCompanion ? [
     {
       title: "Activate this folder locally",
@@ -2602,13 +2618,7 @@ function getCompanionCommands(answers) {
       command: `${COMPANION_NPX_COMMAND} source sync --json`,
       purpose: "Refresh the local snapshot, document dry-run, and code overlay cache after files change."
     }
-  ] : [
-    {
-      title: "Enable local companion workflows",
-      command: `${CREATE_SNIPARA_NPX_COMMAND} repair --with-companion`,
-      purpose: `Install ${COMPANION_PACKAGE_NAME} so this project can run local source activation, folder onboarding, and managed workflow commands without the dashboard.`
-    }
-  ];
+  ] : [];
   const businessOnboardingCommands = answers.installCompanion ? [
     {
       title: "Preview a business folder import",
@@ -2840,8 +2850,8 @@ ${guidance.map((line) => `- ${line}`).join("\n")}
 
 ## Agent Workflow
 
-- At the start of every new thread, validate hosted MCP with a tool-oriented call such as \`snipara_settings\`, \`tools/list\`, or a lightweight \`snipara_context_query\`. Do not treat empty MCP resources/templates as an outage because Snipara may be tool-only.
-- If a session exposes only a subset of expected Snipara tools, call \`snipara_help(list_all=true)\` and compare exact tool names before concluding a tool is unavailable. If only a partial surface remains after exact discovery, use \`snipara-companion recall\`, \`snipara-companion query\`, and \`snipara-companion task-commit\` as a reliable local fallback.
+- At the start of every new thread, validate hosted MCP with a tool-oriented call such as \`snipara_settings\`, \`snipara_help(query=...)\`, or a lightweight \`snipara_context_query\`. Do not treat empty MCP resources/templates as an outage because Snipara may be tool-only.
+- A lean default Snipara tool set is expected. Use \`snipara_help(query=...)\` for routed guidance, \`snipara_help(list_all=true)\` to inspect specialist opt-in surfaces, and \`snipara-companion recall\`, \`snipara-companion query\`, or \`snipara-companion task-commit\` as local fallbacks when the simple tools are unavailable.
 - Start substantial work with \`snipara_recall\` and \`snipara_context_query\`.
 - Use \`answer_pack\` facts, caveats, source maps, and verification checks before making claims.
 - For coding tasks, choose a workflow mode before editing: LITE for small single-phase changes, FULL managed workflow for multi-file, risky, release/deploy, architectural, compaction-prone, or future-maintainer-sensitive work.
@@ -3678,7 +3688,9 @@ function printSuccess(answers, report) {
       chalk.green("   \u2713 Claude Code") + chalk.dim(" - .mcp.json MCP config, .claude/settings.json hooks when enabled")
     );
   }
-  console.log(chalk.green("   \u2713 .snipara/companion") + chalk.dim(" - Local pack + doctor report"));
+  console.log(
+    chalk.green("   \u2713 .snipara/companion") + chalk.dim(" - Doctor report and optional command references")
+  );
   const failedChecks = report.checks.filter((check) => check.status === "fail");
   const warnedChecks = report.checks.filter((check) => check.status === "warn");
   console.log(chalk.bold("\nNext steps:\n"));
@@ -3688,6 +3700,11 @@ function printSuccess(answers, report) {
     nextStep += 1;
   };
   printNextStep("Restart your AI client if you created or changed hosted MCP config.");
+  if (!answers.installCompanion && answers.profile !== "runtime-only") {
+    printNextStep(
+      "Ask your AI client for a first grounded answer using snipara_context_query before enabling local workflow helpers."
+    );
+  }
   if (answers.aiClient === "claude-code") {
     printNextStep(
       "For Claude Code, start a new session and confirm Snipara appears in Settings -> MCP or ToolSearch."
@@ -3712,7 +3729,7 @@ function printSuccess(answers, report) {
       "Restart Codex after changing ~/.codex/config.toml so it rediscovers the hosted Snipara MCP tools."
     );
     printNextStep(
-      "If Codex shows only a minimal Snipara tool set, force discovery for snipara_recall, snipara_context_query, snipara_settings, and any exact htask or swarm tool names you need; confirm the hosted catalog with snipara_help(list_all=true)."
+      "If Codex shows only the lean Snipara tool set, that is expected. Use snipara_help(query=...) for routed guidance, confirm specialist opt-in surfaces with snipara_help(list_all=true), and request exact htask or swarm tools only when the workflow explicitly needs them."
     );
     printNextStep(
       "If Codex still does not expose the hosted task-routing tools, prefer snipara-orchestrator swarm-* and htask-* for shared queue or multi-agent task work."
@@ -3729,11 +3746,11 @@ function printSuccess(answers, report) {
       "For LangChain JavaScript, adapt .snipara/templates/mistral-langchain-tools.ts to bind Snipara recall, context_query, and settings tools to ChatMistralAI."
     );
   }
-  printNextStep("Open .snipara/companion/README.md for local commands and repair flow.");
   printNextStep(
     `Run ${CREATE_SNIPARA_NPX_COMMAND} doctor anytime you want a fresh local validation report.`
   );
   if (answers.installCompanion) {
+    printNextStep("Open .snipara/companion/README.md for local commands and repair flow.");
     printNextStep(
       `${COMPANION_COMMAND_NAME} ${MIN_COMPANION_VERSION}+ is installed for low-latency local hooks.`
     );
@@ -3749,7 +3766,7 @@ function printSuccess(answers, report) {
     );
   } else if (answers.profile !== "runtime-only") {
     printNextStep(
-      `For dashboardless business folder imports, enable companion with: ${CREATE_SNIPARA_NPX_COMMAND} repair --with-companion`
+      `Enable Companion, guards, managed workflows, and local folder helpers later with: ${CREATE_SNIPARA_NPX_COMMAND} repair --with-companion`
     );
   }
   if (answers.installRuntime && !answers.runSandboxInit) {
@@ -3896,7 +3913,7 @@ function resolveMaintenanceProfile(detection, explicitProfile) {
   if (detection.existingConfig.hasSniparaServer) {
     return "hosted-only";
   }
-  return "hosted-companion";
+  return "hosted-only";
 }
 function readApiKeyFromEnvFiles() {
   const candidates = [".env.local", ".env"];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-snipara",
-  "version": "2.0.5",
+  "version": "2.0.7",
   "description": "Onboard Snipara Hosted MCP Context + Memory with auth, companion workflows, and optional Snipara Sandbox",
   "main": "dist/index.js",
   "type": "module",