create-snipara 1.3.12 → 1.3.14

package/README.md

@@ -268,7 +268,7 @@ npx create-snipara --advanced
 npx create-snipara --runtime-only
 
 # Non-interactive setup with an existing API key
-npx create-snipara -y --api-key rlm_xxx --slug my-project
+npx create-snipara -y --api-key snp-xxx --slug my-project
 
 # Open GitHub automation after setup when a GitHub remote is detected
 npx create-snipara --github
@@ -356,9 +356,9 @@ Recommended explanation to users:
 
 ## API Key Requirements
 
-Existing manual API keys passed to `create-snipara --api-key` should start with `rlm_`.
-When `create-snipara` provisions a new account through the browser flow, Snipara returns a
-new `snp-` key from the current hosted API.
+Existing manual API keys passed to `create-snipara --api-key` should start with `snp-`;
+legacy `rlm_` keys remain accepted for migration. When `create-snipara` provisions a
+new account through the browser flow, Snipara returns a new `snp-` key from the current hosted API.
 
 | Tooling                                             | Snipara API key            | LLM API key |
 | --------------------------------------------------- | -------------------------- | ----------- |
@@ -437,7 +437,7 @@ npx create-snipara print-config --json
 When testing a locally packed tarball, use `npm exec --package` instead of `npx`, for example:
 
 ```bash
-npm exec --package ./create-snipara-1.3.12.tgz create-snipara -- --help
+npm exec --package ./create-snipara-1.3.14.tgz create-snipara -- --help
 ```
 
 This avoids `npx` resolution issues with unpublished tarballs.

package/dist/index.js

@@ -9,7 +9,7 @@ import fs from "fs";
 import path from "path";
 import { execSync, spawn } from "child_process";
 import { homedir } from "os";
-var VERSION = "1.3.12";
+var VERSION = "1.3.14";
 var BASE_URL = "https://www.snipara.com";
 var API_URL = "https://api.snipara.com";
 var COMPANION_PACKAGE_NAME = "snipara-companion";
@@ -322,7 +322,7 @@ async function gatherConfiguration(options) {
         {
           title: "I have an API key",
           value: "api",
-          description: "Paste an API key that starts with rlm_"
+          description: "Paste an API key that starts with snp- or legacy rlm_"
         },
         {
           title: "Create free Context + Memory account",
@@ -677,10 +677,11 @@ function sleep(ms) {
   return new Promise((resolve) => setTimeout(resolve, ms));
 }
 function isManualApiKey(value) {
-  return value.trim().startsWith("rlm_");
+  const trimmed = value.trim();
+  return trimmed.startsWith("snp-") || trimmed.startsWith("rlm_");
 }
 function manualApiKeyValidationMessage() {
-  return "API key should start with rlm_";
+  return "API key should start with snp- or legacy rlm_";
 }
 function isProvisionedApiKey(value) {
   return value.trim().startsWith("snp-");
@@ -1693,13 +1694,12 @@ async function testHostedConnection(answers) {
         }
       ];
     }
-    const toolCount = toolsResponse.data.result?.tools?.length || 0;
-    spinner.succeed(`Connected! ${toolCount} MCP tools available.`);
+    spinner.succeed("Connected to Snipara Hosted MCP.");
     const checks = [
       {
         name: "hosted_connection",
         status: "pass",
-        detail: `tools/list succeeded (${toolCount} tools reported)`
+        detail: "tools/list succeeded"
       }
     ];
     const settingsResponse = await callHostedMcp(answers, "tools/call", {

package/package.json

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