@mtreeai/msapling-cli 2.3.6-beta.34 → 2.3.6-beta.36

package/README.md

@@ -1,168 +1,168 @@
-# MSapling CLI
-
-MSapling CLI is the React/TypeScript terminal client for the MSapling backend.
-
-## Install
-
-Install the MSapling CLI globally via npm:
-
-```bash
-npm install -g @msapling/cli
-```
-
-**Requirements:** Node.js 18 or higher.
-
-**Note:** Version 2.3.3+ is the first npm-installable release with email/password login support. See [@msapling/cli on npm](https://www.npmjs.com/package/@msapling/cli) for the latest version.
-
-## First Run
-
-Start the interactive REPL:
-
-```bash
-msapling
-```
-
-Inside the REPL, authenticate using one of these methods:
-
-```
-/login your@email.com    # Email + password login (with optional 2FA)
-/login github            # GitHub device flow (opens browser)
-/login <token>           # Paste an API token from msapling.com Settings
-```
-
-All methods store the token via the OS keychain (Windows DPAPI, macOS Keychain, or Linux libsecret).
-
-Once logged in, start chatting:
-
-```
-/chat hello
-```
-
-## CLI Subcommands (argv)
-
-These are passed directly on the command line before the REPL starts:
-
-| Command | Description |
-|---------|-------------|
-| *(none)* | Start interactive REPL |
-| `--compact` | Start REPL in compact mode (thin separators, no footer) |
-| `mcp serve` | Run as MCP stdio server (Claude Code / Cursor / Windsurf integration) |
-| `--version` | Print version and exit |
-| `--help` | Print usage and exit |
-
-## Inside the REPL — Slash Commands
-
-Once the REPL is running, type `/help` to see all available slash commands. Common ones:
-
-| Slash Command | Description |
-|---------------|-------------|
-| `/login your@email.com` | Sign in with email + password (recommended for end users) |
-| `/login github` | GitHub device flow (for developers) |
-| `/login <token>` | Paste an API token from Settings → API Keys |
-| `/logout` | Clear stored token |
-| `/chat <message>` | Send a message and stream a response |
-| `/swarm <prompt>` | Run parallel agent swarms |
-| `/models` | List available models |
-| `/cost` | Show usage and billing data |
-| `/config` | View and edit configuration |
-| `/help` | Show all slash-command help |
-
-> **Note:** `chat`, `login`, `models`, `cost`, `swarm`, and `config` are REPL slash-commands (prefixed with `/`), not top-level argv subcommands. Run `msapling --help` to see the argv interface.
-
-See `packages/cli/src/commands/index.ts` for the canonical slash-command list.
-
----
-
-
-
-The CLI is not meant to be a large standalone agent runtime. MSapling's backend is the source of truth for auth, projects, chats, model routing, usage, billing, MDrive, locks, and audit data. The website, mobile app, and CLI should all show and modify the same backend state.
-
-## Product Direction
-
-MSapling started as a multi-chat browser workspace: multiple AI chats, many model choices, BYOK, OpenRouter, and Ollama support in one UI.
-
-The mobile app extends that shared workspace to one-chat-at-a-time usage and phone-first workflows such as sending a photo into a chat.
-
-The CLI brings the same backend workspace to the terminal. It should be fast, low-resource, and useful without duplicating the backend.
-
-## Architecture
-
-```text
-Website     \
-Mobile App   ->  MSapling Backend  ->  chats, projects, usage, billing, MDrive, locks
-CLI         /
-```
-
-The CLI should:
-
-- authenticate with the backend
-- read projects and chats from the backend
-- stream chat responses from `/api/chat/message`
-- display backend usage and quota data
-- respect backend stream locks
-- use backend MDrive/edit proposal flows
-- keep local terminal work lightweight
-
-The CLI should not:
-
-- invent separate chat state
-- compute billing locally
-- simulate MDrive state
-- bypass backend locks
-- duplicate backend orchestration unless there is a clear reason
-
-## Current State
-
-This directory is a Bun monorepo scaffold using React and Ink.
-
-Port useful behavior selectively. Do not port backend-like responsibilities.
-
-Known current gaps:
-
-- workspace package manifests are missing
-- the Ink input loop is incomplete
-- `Agent` is referenced but not implemented
-- MDrive logic is simulated locally
-- backend route contracts need to be aligned
-- tests and build are not yet passing
-
-## Near-Term Goal
-
-Build a stable thin client:
-
-1. Login and secure token storage.
-2. Fetch backend project overview.
-3. Open or create chats.
-4. Stream backend chat responses.
-5. Show shared chat history across website, app, and CLI.
-6. Handle lock, quota, and auth errors clearly.
-7. Add `/doctor`.
-
-## Commands
-
-```bash
-bun install
-bun run build
-bun test
-bun run start
-```
-
-These commands are target commands. They may not pass until the workspace manifests and dependencies are completed.
-
-## Environment
-
-```bash
-MSAPLING_API_URL=https://api.msapling.com
-```
-
-For local development, point `MSAPLING_API_URL` at the local backend.
-
-## Design Principle
-
-Keep the CLI small.
-
-The backend should do the heavy work. The CLI should make that backend fast and comfortable from a terminal.
-
----
-
-**Full architecture overview:** see ARCHITECTURE.md (when published) or `packages/core/README.md`.
+# MSapling CLI
+
+MSapling CLI is the React/TypeScript terminal client for the MSapling backend.
+
+## Install
+
+Install the MSapling CLI globally via npm:
+
+```bash
+npm install -g @mtreeai/msapling-cli@beta
+```
+
+**Requirements:** Node.js 20.10 or higher.
+
+**Note:** This is a private/internal package (restricted access). Internal testers should `npm install -g @mtreeai/msapling-cli@beta`. See [@mtreeai/msapling-cli on npm](https://www.npmjs.com/package/@mtreeai/msapling-cli) for the latest version.
+
+## First Run
+
+Start the interactive REPL:
+
+```bash
+msapling
+```
+
+Inside the REPL, authenticate using one of these methods:
+
+```
+/login your@email.com    # Email + password login (with optional 2FA)
+/login github            # GitHub device flow (opens browser)
+/login <token>           # Paste an API token from msapling.com Settings
+```
+
+All methods store the token via the OS keychain (Windows DPAPI, macOS Keychain, or Linux libsecret).
+
+Once logged in, start chatting:
+
+```
+/chat hello
+```
+
+## CLI Subcommands (argv)
+
+These are passed directly on the command line before the REPL starts:
+
+| Command | Description |
+|---------|-------------|
+| *(none)* | Start interactive REPL |
+| `--compact` | Start REPL in compact mode (thin separators, no footer) |
+| `mcp serve` | Run as MCP stdio server (Claude Code / Cursor / Windsurf integration) |
+| `--version` | Print version and exit |
+| `--help` | Print usage and exit |
+
+## Inside the REPL — Slash Commands
+
+Once the REPL is running, type `/help` to see all available slash commands. Common ones:
+
+| Slash Command | Description |
+|---------------|-------------|
+| `/login your@email.com` | Sign in with email + password (recommended for end users) |
+| `/login github` | GitHub device flow (for developers) |
+| `/login <token>` | Paste an API token from Settings → API Keys |
+| `/logout` | Clear stored token |
+| `/chat <message>` | Send a message and stream a response |
+| `/swarm <prompt>` | Run parallel agent swarms |
+| `/models` | List available models |
+| `/cost` | Show usage and billing data |
+| `/config` | View and edit configuration |
+| `/help` | Show all slash-command help |
+
+> **Note:** `chat`, `login`, `models`, `cost`, `swarm`, and `config` are REPL slash-commands (prefixed with `/`), not top-level argv subcommands. Run `msapling --help` to see the argv interface.
+
+See `packages/cli/src/commands/index.ts` for the canonical slash-command list.
+
+---
+
+
+
+The CLI is not meant to be a large standalone agent runtime. MSapling's backend is the source of truth for auth, projects, chats, model routing, usage, billing, MDrive, locks, and audit data. The website, mobile app, and CLI should all show and modify the same backend state.
+
+## Product Direction
+
+MSapling started as a multi-chat browser workspace: multiple AI chats, many model choices, BYOK, OpenRouter, and Ollama support in one UI.
+
+The mobile app extends that shared workspace to one-chat-at-a-time usage and phone-first workflows such as sending a photo into a chat.
+
+The CLI brings the same backend workspace to the terminal. It should be fast, low-resource, and useful without duplicating the backend.
+
+## Architecture
+
+```text
+Website     \
+Mobile App   ->  MSapling Backend  ->  chats, projects, usage, billing, MDrive, locks
+CLI         /
+```
+
+The CLI should:
+
+- authenticate with the backend
+- read projects and chats from the backend
+- stream chat responses from `/api/chat/message`
+- display backend usage and quota data
+- respect backend stream locks
+- use backend MDrive/edit proposal flows
+- keep local terminal work lightweight
+
+The CLI should not:
+
+- invent separate chat state
+- compute billing locally
+- simulate MDrive state
+- bypass backend locks
+- duplicate backend orchestration unless there is a clear reason
+
+## Current State
+
+This directory is a Bun monorepo scaffold using React and Ink.
+
+Port useful behavior selectively. Do not port backend-like responsibilities.
+
+Known current gaps:
+
+- workspace package manifests are missing
+- the Ink input loop is incomplete
+- `Agent` is referenced but not implemented
+- MDrive logic is simulated locally
+- backend route contracts need to be aligned
+- tests and build are not yet passing
+
+## Near-Term Goal
+
+Build a stable thin client:
+
+1. Login and secure token storage.
+2. Fetch backend project overview.
+3. Open or create chats.
+4. Stream backend chat responses.
+5. Show shared chat history across website, app, and CLI.
+6. Handle lock, quota, and auth errors clearly.
+7. Add `/doctor`.
+
+## Commands
+
+```bash
+bun install
+bun run build
+bun test
+bun run start
+```
+
+These commands are target commands. They may not pass until the workspace manifests and dependencies are completed.
+
+## Environment
+
+```bash
+MSAPLING_API_URL=https://api.msapling.com
+```
+
+For local development, point `MSAPLING_API_URL` at the local backend.
+
+## Design Principle
+
+Keep the CLI small.
+
+The backend should do the heavy work. The CLI should make that backend fast and comfortable from a terminal.
+
+---
+
+**Full architecture overview:** see ARCHITECTURE.md (when published) or `packages/core/README.md`.

package/dist/index.js

@@ -11936,8 +11936,8 @@ function formatTable(results) {
     const model = r.model.slice(0, 39).padEnd(40);
     const ttft = r.ttft_ms != null ? r.ttft_ms.toFixed(0).padStart(9) : "    -    ";
     const tps = r.tps != null ? r.tps.toFixed(1).padStart(7) : "     -  ";
-    const tok = r.total_tokens.toString().padStart(8);
-    const cost = r.cost_usd.toFixed(5).padStart(9);
+    const tok = (r.total_tokens ?? 0).toString().padStart(8);
+    const cost = (typeof r.cost_usd === "number" ? r.cost_usd : 0).toFixed(5).padStart(9);
     const err = r.error ? `  \u26A0 ${r.error}` : "";
     return `${model} ${ttft} ${tps} ${tok} ${cost}${err}`;
   });
@@ -12370,7 +12370,7 @@ var init_version = __esm({
       description: "Show version information for CLI and core packages",
       category: "debug",
       handler: async (_args, context) => {
-        const cliVersion = true ? "2.3.6-beta.34" : "(dev)";
+        const cliVersion = true ? "2.3.6-beta.36" : "(dev)";
         const coreVersion = true ? "2.3.2" : "(dev)";
         const runtime = process.version;
         context.addMessage("system", "MSapling Version Info");
@@ -12379,7 +12379,7 @@ var init_version = __esm({
         context.addMessage("system", row2("Core (@msapling/core)", coreVersion));
         context.addMessage("system", row2("Runtime (Node/Bun)", runtime));
         try {
-          const ts = "2026-06-02T15:12:47.326Z";
+          const ts = "2026-06-02T15:16:34.864Z";
           if (ts && ts !== "__BUILD_TIMESTAMP__") {
             context.addMessage("system", row2("Build Timestamp", ts));
           }
@@ -13111,11 +13111,12 @@ var init_budget = __esm({
         try {
           const data = await context.client.getBillingBuckets();
           context.addMessage("system", "Budget Buckets:");
+          const n = (v) => typeof v === "number" && Number.isFinite(v) ? v : Number(v) || 0;
           if (data && typeof data === "object") {
             for (const [key, val] of Object.entries(data)) {
               const bucket = val;
-              const remaining = bucket.remaining ?? bucket.balance ?? 0;
-              const limit = bucket.limit ?? bucket.cap ?? 0;
+              const remaining = n(bucket?.remaining ?? bucket?.balance);
+              const limit = n(bucket?.limit ?? bucket?.cap);
               context.addMessage("system", `  - ${key}: $${remaining.toFixed(4)} / $${limit.toFixed(4)}`);
             }
           } else {
@@ -17896,7 +17897,7 @@ import { jsx, jsxs } from "react/jsx-runtime";
 var Header = () => /* @__PURE__ */ jsxs(Box, { borderStyle: "single", borderColor: "cyan", paddingX: 1, marginBottom: 1, children: [
   /* @__PURE__ */ jsxs(Text, { bold: true, color: "cyan", children: [
     "\u25CF MSapling CLI v",
-    "2.3.6-beta.34"
+    "2.3.6-beta.36"
   ] }),
   /* @__PURE__ */ jsx(Box, { marginLeft: 2, children: /* @__PURE__ */ jsx(Text, { color: "gray", children: "Platinum Tier Architecture" }) })
 ] });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mtreeai/msapling-cli",
-  "version": "2.3.6-beta.34",
+  "version": "2.3.6-beta.36",
   "description": "MSapling CLI — React/Ink terminal client for the MSapling backend (chat, projects, MDrive, agent tools). Proprietary; redistribution prohibited.",
   "license": "UNLICENSED",
   "author": "MSapling Team",