@xevy/cli 0.1.5 → 0.1.7

package/README.md

@@ -1,18 +1,81 @@
 # @xevy/cli
 
-The **`xevy`** command — set up and launch the [pi](https://github.com/badlogic/pi-mono) agent with Xevy.
+The **`xevy`** command — set up and launch the [pi](https://github.com/badlogic/pi-mono) agent with Xevy, the free AI workspace for digital business.
+
+New here? Follow **Get started** below from top to bottom — it takes about five minutes.
+
+## Get started
+
+### 1. Create your Xevy account
+
+Xevy is free. Register (or log in if you already have an account) in the browser first:
+
+- **Register:** <https://xevy.ai/register>
+- **Log in:** <https://xevy.ai/login>
+
+### 2. Make sure you have Node.js
+
+The CLI runs on [Node.js](https://nodejs.org/) 18 or newer. Check what you have:
+
+```bash
+node --version   # should print v18.x.x or higher
+```
+
+If the command isn't found or the version is too old, install the latest LTS from
+<https://nodejs.org/> and try again. `npm` ships with Node, so you get it automatically.
+
+### 3. Install the CLI
+
+Install globally so the `xevy` command is available everywhere on your machine:
+
+```bash
+npm install -g @xevy/cli
+```
+
+> Prefer not to install anything? You can run every command below with `npx @xevy/cli`
+> instead of `xevy` — e.g. `npx @xevy/cli setup`. It's slower each run but installs nothing.
+
+### 4. Run the one-time setup
 
 ```bash
-npx @xevy/cli setup   # one-time: install pi + the Xevy extension + your API key
-npx @xevy/cli         # open pi with the Xevy extension loaded
+xevy setup
+```
+
+This walks you through everything:
+
+1. Installs the **pi agent** if it isn't already on your PATH.
+2. Installs the Xevy extensions (see [`xevy setup`](#xevy-setup) for details).
+3. Asks for your **API key**. When prompted, open the link it prints — it takes you
+   straight to **Settings → Profile → API keys** at
+   <https://xevy.ai/settings?section=profile&tab=api> — click **Create key**, copy the
+   key, and paste it back into the terminal. Your key is saved to
+   `~/.config/xevy/credentials` and never printed again.
+
+### 5. Start working
+
+```bash
+xevy                        # open an interactive pi session with Xevy loaded
+xevy "summarise this repo"  # or send a one-off prompt
+```
+
+That's it — you're set up. The sections below are reference for when you need more detail.
+
+## Upgrading
+
+```bash
+npm update -g @xevy/cli    # or re-run: npm install -g @xevy/cli
 ```
 
 ## `xevy setup`
 
 1. Installs the **pi agent** if it isn't already on your PATH.
-2. Downloads the Xevy pi extension (`xevy.ts`) into **`~/.xevy/extensions/`**.
-3. Asks for your **API key** and prints a **direct link to the API-keys tab** so
-   you can generate one in a couple of clicks, then stores it in
+2. Installs the Xevy extensions:
+   - **`xevy-core.ts`** (shared UI + setup/context), **`xevy-model.ts`** (the
+     `xevy/*` models), and **`xevy-mcp.ts`** (the MCP→pi tool bridge) into pi's
+     **global** dir `~/.pi/agent/extensions/`, so they load in *every* pi session.
+   - **`xevy.ts`** (tools + workflow commands) into **`~/.xevy/extensions/`**.
+3. Asks for your **API key** (reuses an already-saved one if present) and prints a
+   **direct link to the API-keys tab** to generate one, then stores it in
    `~/.config/xevy/credentials` (mode `600`, never printed).
 
 The API-keys link opens **Settings → Profile → API keys** directly:
@@ -20,21 +83,14 @@ The API-keys link opens **Settings → Profile → API keys** directly:
 
 ## `xevy`
 
-Opens pi, loading every `*.ts` extension in `~/.xevy/extensions` (`pi -e …`).
-Any extra arguments are forwarded to pi:
+Opens pi, loading `~/.xevy/extensions` via `pi -e …` (pi also auto-loads the
+global dir, so core + model + MCP come along). Extra arguments are forwarded to pi:
 
 ```bash
 xevy                       # interactive pi session with Xevy
 xevy "summarise this repo" # forwards the prompt to pi
 ```
 
-## `xevy pi` (alternative)
-
-Installs the split **model + MCP** extensions (`xevy-model.ts`, `xevy-mcp.ts`)
-into pi's own extensions dir and authenticates over **OAuth** (`/login xevy`) —
-no API key. Use this instead of `setup` if you prefer OAuth and the hosted
-`xevy/*` models + MCP tool bridge.
-
 ## Options
 
 ```
@@ -43,8 +99,20 @@ no API key. Use this instead of `setup` if you prefer OAuth and the hosted
   -h, --help         Show help
 ```
 
+## Skills & MCP for other agents
+
+`@xevy/cli` sets up the [pi](https://github.com/badlogic/pi-mono) agent. If you'd
+rather use **Cursor, Claude Code, or one of [50+ other agents](https://github.com/vercel-labs/skills#supported-agents)**,
+install the Xevy **SDLC skills** and the **Xevy MCP server** with the sibling
+package instead:
+
 ```bash
-XEVY_BASE=https://xevy.vyte.dev npx @xevy/cli setup
+npx @xevy/skills          # skills + MCP, global by default
+npx @xevy/skills --project # into the current repo instead
 ```
 
+Then connect MCP over OAuth (Cursor: Settings → MCP → `xevy`; Claude Code: browser
+sign-in on first use). See the [`@xevy/skills` README](../xevy-skills/README.md) for
+the full command list, per-agent flags, and manual install steps.
+
 Docs: <https://xevy.ai/docs/mcp>

package/bin/xevy.mjs

@@ -2,15 +2,14 @@
 /**
  * @xevy/cli — the `xevy` command.
  *
- *   xevy setup   Install the pi agent (if missing), download the Xevy pi
- *                extension into ~/.xevy/extensions, and store your API key.
- *   xevy         Open pi with the Xevy extensions from ~/.xevy/extensions.
- *   xevy pi      (alt) Install the split model + MCP extensions into pi's own
- *                extensions dir, authenticated via OAuth.
+ *   xevy setup   Install the pi agent (if missing); install the Xevy extensions
+ *                (core + model + MCP globally, xevy.ts into ~/.xevy/extensions);
+ *                and store your API key.
+ *   xevy         Open pi with the Xevy extensions.
  *
- * `xevy setup` is the default flow: it fetches `xevy.ts` from the server and
- * asks for an API key (with a direct link to the exact page to generate one),
- * stored in ~/.config/xevy/credentials. Then `xevy` launches pi with it.
+ * `xevy setup` fetches the extensions from the server and asks for an API key
+ * (with a direct link to the exact page to generate one), stored in
+ * ~/.config/xevy/credentials. Then `xevy` launches pi with them.
  */
 import { spawnSync } from "node:child_process";
 import fs from "node:fs";
@@ -40,12 +39,9 @@ const CREDENTIALS_DIR = path.join(
 );
 const CREDENTIALS_FILE = path.join(CREDENTIALS_DIR, "credentials");
 
-// `xevy pi` (alt flow) installs these into pi's own extensions dir over OAuth.
+// pi's global extensions dir — core + model + MCP are installed here so they
+// load in every pi session.
 const PI_EXTENSION_DIR = path.join(os.homedir(), ".pi", "agent", "extensions");
-const PI_EXTENSIONS = [
-  { file: "xevy-model.ts", marker: "xevyModelExtension" },
-  { file: "xevy-mcp.ts", marker: "xevyMcpExtension" },
-];
 
 function apiKeysUrl(base) {
   // Direct link to the API keys tab (Profile → API keys), reachable without a
@@ -71,8 +67,7 @@ function usage() {
   console.log(`Xevy CLI
 
   xevy                   Open pi with the Xevy extensions in ~/.xevy/extensions
-  xevy setup [--base u]  Install pi (if missing) + the Xevy pi extension, store your API key
-  xevy pi [--base u]     (alt) Install the split model + MCP extensions over OAuth
+  xevy setup [--base u]  Install pi (if missing) + the Xevy extensions, store your API key
 
 Options:
       --base <url>       Xevy host (default: XEVY_BASE or ${DEFAULT_BASE})
@@ -82,7 +77,11 @@ Options:
 Examples:
   npx @xevy/cli setup
   npx @xevy/cli
-  XEVY_BASE=https://xevy.vyte.dev npx @xevy/cli setup`);
+
+Install globally to drop the npx prefix:
+  npm install -g @xevy/cli
+  xevy setup
+  xevy`);
 }
 
 function parseArgv(argv) {
@@ -95,9 +94,9 @@ function parseArgv(argv) {
   if (first === "-h" || first === "--help" || first === "help") return { command: "help", base };
   if (first === "-v" || first === "--version") return { command: "version", base };
 
-  if (first === "setup" || first === "pi") {
+  if (first === "setup") {
     args.shift();
-    const opts = { command: first, base, piArgs: [] };
+    const opts = { command: "setup", base, piArgs: [] };
     while (args.length > 0) {
       const a = args.shift();
       if (a === "--base") {
@@ -106,7 +105,7 @@ function parseArgv(argv) {
         opts.base = v.replace(/\/$/, "");
         continue;
       }
-      die(`Unknown option for \`xevy ${first}\`: ${a}. Try \`xevy --help\`.`);
+      die(`Unknown option for \`xevy setup\`: ${a}. Try \`xevy --help\`.`);
     }
     return opts;
   }
@@ -246,8 +245,10 @@ async function setup(opts) {
   //      double-load: if it were also in ~/.xevy it'd register ask_question twice.
   //    • xevy-model.ts → GLOBAL too, so the xevy/* models are available in every
   //      pi session (plain `pi` included), not just via `xevy`.
+  //    • xevy-mcp.ts   → GLOBAL too — the MCP→pi tool bridge (auth reused from
+  //      the model login), available in every pi session.
   //    • xevy.ts       → ~/.xevy/extensions (tools/workflow; loaded by `xevy`,
-  //      which also auto-loads the global dir → core + model come along).
+  //      which also auto-loads the global dir → core + model + MCP come along).
   await downloadExtension(opts.base, "xevy-core.ts", PI_EXTENSION_DIR, [
     "xevyCoreExtension",
     "registerCommand",
@@ -256,6 +257,10 @@ async function setup(opts) {
     "xevyModelExtension",
     "registerCommand",
   ]);
+  await downloadExtension(opts.base, "xevy-mcp.ts", PI_EXTENSION_DIR, [
+    "xevyMcpExtension",
+    "registerCommand",
+  ]);
   await downloadExtension(opts.base, XEVY_EXTENSION_FILE, XEVY_EXTENSIONS_DIR, [
     "EXTENSION_VERSION",
     "registerCommand",
@@ -275,7 +280,7 @@ async function setup(opts) {
   console.log(`✓ API key stored at ${CREDENTIALS_FILE} (key not shown).`);
 
   console.log("\n✓ Setup complete.");
-  console.log("  • Xevy models (xevy/auto, xevy/fast, …) are available in any pi session — no /login needed.");
+  console.log("  • Xevy models (xevy/auto, xevy/fast, …) + MCP tools are available in any pi session — no /login needed.");
   console.log("  • Run `xevy` to open pi with the Xevy tools + models loaded.");
   if (opts.base !== DEFAULT_BASE) console.log(`  • Host: ${opts.base}`);
 }
@@ -304,29 +309,12 @@ function open(opts) {
   process.exit(r.status ?? 0);
 }
 
-async function piSetup(opts) {
-  console.log("Setting up the pi agent + Xevy extensions (model + MCP)\n");
-
-  ensurePi();
-  for (const ext of PI_EXTENSIONS) {
-    await downloadExtension(opts.base, ext.file, PI_EXTENSION_DIR, [ext.marker, "registerCommand"]);
-  }
-
-  console.log("\n✓ pi + Xevy extensions ready.");
-  console.log("  • Sign in once: /login xevy — authenticates both the models and the MCP tools.");
-  console.log("  • Xevy models: xevy/auto, xevy/fast, xevy/advance, xevy/min, xevy/max, xevy/vision.");
-  console.log("  • MCP tools bridge automatically on session start (or run /xevy-mcp).");
-  console.log("  • If pi is already running, use /reload to load the extensions.");
-  if (opts.base !== DEFAULT_BASE) console.log(`  • Source host: ${opts.base}`);
-}
-
 async function main() {
   const opts = parseArgv(process.argv.slice(2));
 
   if (opts.command === "help") return usage();
   if (opts.command === "version") return console.log(readCliVersion());
   if (opts.command === "setup") return setup(opts);
-  if (opts.command === "pi") return piSetup(opts);
   if (opts.command === "open") return open(opts);
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xevy/cli",
-  "version": "0.1.5",
+  "version": "0.1.7",
   "description": "Xevy CLI — `xevy setup` installs the pi agent + the Xevy pi extension and stores your API key; `xevy` opens pi with it.",
   "type": "module",
   "keywords": [