@opennous/cli 0.7.1 → 0.7.4

package/README.md

@@ -4,18 +4,14 @@ Nous CLI — set Nous up, connect it to your coding agent, and read the Context
 
 ## Get started
 
-```bash
-curl -fsSL https://api.opennous.cloud/install | sh
-```
-
-That installs the CLI and runs `nous init`, which signs you in (creating your account if you don't have one), registers the Nous MCP server with the agent on your machine, and hands off. Then tell your agent *"set up my Nous workspace"* — it reads your project, finds your ICP (or drafts one), and syncs it.
-
-Prefer to run it yourself:
+One command. It signs you in (creating your account if you don't have one), registers the Nous MCP server with the agent on your machine, and hands off. The same command on macOS, Linux, and Windows (needs [Node 18+](https://nodejs.org)):
 
 ```bash
-npx -y @opennous/cli@latest init
+npx @opennous/cli@latest init
 ```
 
+Then tell your agent *"set up my Nous workspace"* — it reads your project, finds your ICP (or drafts one), and syncs it. On self-host, add `--url https://api.yourdomain.com`.
+
 ## Event tracking
 
 `nous track init` detects your stack (Next.js, Node, Python), writes a small `nous.js` (or `nous.py`) module with three helpers, and updates your `.env`:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@opennous/cli",
-  "version": "0.7.1",
+  "version": "0.7.4",
   "description": "Nous CLI — set up Nous, connect it to your coding agent, and read the Context API from your terminal",
   "type": "module",
   "bin": {

package/src/index.js

@@ -8,7 +8,7 @@
 import { program, Command } from "commander";
 import { readFileSync, writeFileSync, existsSync, mkdirSync, appendFileSync } from "fs";
 import { homedir } from "os";
-import { join, resolve } from "path";
+import { join, resolve, dirname } from "path";
 import { createInterface } from "readline";
 import { spawn, spawnSync } from "child_process";
 
@@ -32,12 +32,16 @@ function openBrowser(url) {
   if (process.platform === "darwin") {
     cmd = "open"; args = [url];
   } else if (process.platform === "win32") {
-    // cmd.exe /c start "" "<url>". The empty "" is start's title argument (else a
-    // quoted URL is taken as the window title). windowsVerbatimArguments keeps the
-    // quotes we add, so an & in the auth URL's query string stays inside them and
-    // isn't parsed by cmd as a command separator.
+    // cmd.exe /c start "" "<url>". `start` reads a lone quoted arg as the window
+    // TITLE, so it needs an explicit empty title before the URL — otherwise it just
+    // opens a shell titled with the URL and never launches the browser.
+    // CRITICAL: the title must be a LITERAL `""` string, not JS's zero-length "".
+    // With windowsVerbatimArguments the args are joined by spaces as-is, so a
+    // zero-length string collapses to nothing and the title is lost (the URL then
+    // becomes the title). Verbatim also keeps our quotes, so an & in the auth URL's
+    // query string stays inside them and isn't parsed by cmd as a command separator.
     cmd = process.env.ComSpec || "cmd.exe";
-    args = ["/c", "start", "", `"${url}"`];
+    args = ["/c", "start", '""', `"${url}"`];
     opts.windowsVerbatimArguments = true;
   } else {
     cmd = "xdg-open"; args = [url];
@@ -831,7 +835,7 @@ program
 // ---------------------------------------------------------------------------
 // Browser sign-in (device authorization). Opens the browser, you approve, and a
 // freshly minted API key is saved to ~/.nous/config.json. No copy-paste. Shared
-// by `nous login`, `nous init`, and the plugin's /nous-login command.
+// by `nous login` and `nous init`.
 // ---------------------------------------------------------------------------
 async function browserLogin(url) {
   const apiUrl = url || process.env.NOUS_API_URL || readConfig().apiUrl || "https://api.opennous.cloud";
@@ -894,10 +898,11 @@ program
 // ---------------------------------------------------------------------------
 // MCP registration — connect Nous to whatever agent is on this machine.
 //
-// We deliberately DO NOT use the Claude Code plugin/marketplace here. Two commands
-// (`/plugin marketplace add`, `/plugin install`), Claude-Code-only, with a marketplace
-// standing between a new user and the product — it's too much for a first run. The MCP
-// server is the whole integration, and `claude mcp add` registers it in one line.
+// There is deliberately no Claude Code plugin/marketplace. A plugin would be Claude-Code-only
+// and put a marketplace between a new user and the product — too much for a first run, and it
+// wouldn't work for Cursor, Codex, or any other host. The MCP server is the whole integration,
+// so registration is one cross-platform step: `claude mcp add` if the Claude CLI is here, else
+// a `.mcp.json` any MCP host reads.
 //
 // The MCP resolves its key from ~/.nous/config.json on every call, so we never bake the
 // key into any of these configs — sign-in already wrote it there.
@@ -927,7 +932,7 @@ function writeJsonMcp(path, apiUrl) {
     // Only pin a non-default API URL (self-host). Cloud reads the key from the config file.
     ...(apiUrl && apiUrl !== "https://api.opennous.cloud" ? { env: { NOUS_API_URL: apiUrl } } : {}),
   };
-  const dir = path.slice(0, path.lastIndexOf("/"));
+  const dir = dirname(path);
   if (dir && !existsSync(dir)) mkdirSync(dir, { recursive: true });
   writeFileSync(path, JSON.stringify(cfg, null, 2) + "\n");
 }
@@ -977,8 +982,8 @@ program
       }
     }
 
-    console.log('\nYou\'re set. Tell your agent: "set up my GTM context layer and connect it to');
-    console.log("Nous\" — it audits your project's context, drafts what's missing, and syncs it.\n");
+    console.log("\nYou're set. Tell your agent:\n");
+    console.log('  "set up my Nous workspace and walk me through onboarding"\n');
     console.log(dim("Docs: https://docs.opennous.cloud/mcp/introduction"));
   });