vault-cortex 0.2.3 → 0.2.5

package/dist/init.js

@@ -4,7 +4,7 @@ import { buildLocalConnectMessage, buildRemoteConnectMessage, } from "./messages
 import { OBSIDIAN_SYNC_IMAGE, pollHealth } from "./docker.js";
 import { buildFilesToWrite, readEnvPort, writeFiles, } from "./scaffold.js";
 import { generateToken } from "./token.js";
-import { validateVaultPath } from "./vault.js";
+import { expandTilde, validateVaultPath } from "./vault.js";
 const DEFAULT_TARGET_DIR = "./vault-cortex";
 const isMode = (value) => value === "local" || value === "remote";
 const askMode = async (prompts) => {
@@ -169,13 +169,15 @@ const runLocalInit = async (flags, deps) => {
     const vaultPath = vaultPathResult !== undefined && vaultPathResult.kind !== "error"
         ? vaultPathResult.path
         : await askVaultPath(prompts);
-    const targetDir = resolve(flags.dir ??
+    // expandTilde before resolve: resolve() treats a leading `~` as a literal
+    // path segment, so a quoted "~/path" would create a directory named "~".
+    const targetDir = resolve(expandTilde(flags.dir ??
         (flags.yes
             ? DEFAULT_TARGET_DIR
             : await prompts.text("Where should I put the config files?", {
                 defaultValue: DEFAULT_TARGET_DIR,
                 placeholder: DEFAULT_TARGET_DIR,
-            })));
+            }))));
     const token = generateToken();
     // Conflict policy: identical existing files are skipped silently;
     // differing ones prompt per file (default keep). --yes never overwrites —
@@ -211,11 +213,13 @@ const runLocalInit = async (flags, deps) => {
 // instructions. Always interactive — the sync-token step can't be defaulted.
 const runRemoteInit = async (flags, deps) => {
     const { prompts, docker } = deps;
-    const targetDir = resolve(flags.dir ??
+    // expandTilde before resolve: resolve() treats a leading `~` as a literal
+    // path segment, so a quoted "~/path" would create a directory named "~".
+    const targetDir = resolve(expandTilde(flags.dir ??
         (await prompts.text("Where should I put the config files?", {
             defaultValue: DEFAULT_TARGET_DIR,
             placeholder: DEFAULT_TARGET_DIR,
-        })));
+        }))));
     const publicUrl = await askPublicUrl(prompts);
     const vaultName = await askVaultName(prompts);
     // The Obsidian Sync token comes from an interactive docker run (the

package/dist/messages.js

@@ -22,8 +22,11 @@ export const buildLocalConnectMessage = (params) => {
     const startLine = started
         ? "The server is running."
         : startServerLine(targetDir);
+    // When the token was written, put it alone on its own line so selecting
+    // that line copies just the token — no "Auth token: " prefix to trim and
+    // no chance of grabbing the surrounding label.
     const tokenLine = tokenWritten
-        ? `Auth token: ${token}`
+        ? `Auth token:\n  ${token}`
         : `Auth token: use the existing MCP_AUTH_TOKEN in ${targetDir}/.env`;
     // Flush-left on purpose: template literals keep leading whitespace, so
     // indenting these lines would indent the rendered output.
@@ -34,7 +37,9 @@ Connect your MCP client:
   ${tokenLine}
 
 Claude Code:
-  1. claude mcp add --transport http vault-cortex http://localhost:${port}/mcp
+  1. claude mcp add --scope user --transport http vault-cortex http://localhost:${port}/mcp
+     (--scope user registers it for every project; drop it to scope
+     the server to the current directory only)
   2. Approve the browser consent page with the token above
   3. Done. The client holds auto-refreshing access tokens; the
      token never sits in client config
@@ -89,7 +94,7 @@ export const buildRemoteConnectMessage = (params) => {
 Note: claude.ai and Claude Desktop only accept https URLs — set up
 HTTPS when you're ready for those clients (see the HTTPS section in
 the remote guide). Claude Code works with http:
-  claude mcp add --transport http vault-cortex ${publicUrl}/mcp`;
+  claude mcp add --scope user --transport http vault-cortex ${publicUrl}/mcp`;
     // Flush-left on purpose: template literals keep leading whitespace, so
     // indenting these lines would indent the rendered output.
     const connectMessage = `${startLine}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vault-cortex",
-  "version": "0.2.3",
+  "version": "0.2.5",
   "description": "Set up a Vault Cortex MCP server for your Obsidian vault in one command: npx vault-cortex init",
   "license": "MIT",
   "type": "module",