@mtreeai/msapling-cli 2.3.6-beta.50 → 2.3.6-beta.51
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +9 -6
- package/dist/index.js +15092 -9780
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -61,13 +61,15 @@ Once the REPL is running, type `/help` to see all available slash commands. Comm
|
|
|
61
61
|
| `/login <token>` | Paste an API token from Settings → API Keys |
|
|
62
62
|
| `/logout` | Clear stored token |
|
|
63
63
|
| `/chat <message>` | Send a message and stream a response |
|
|
64
|
-
| `/
|
|
65
|
-
| `/
|
|
64
|
+
| `/chat new <title>` | Create a chat inside the fixed CLI project |
|
|
65
|
+
| `/chat import <chat_id>` | Copy another owned chat into a new CLI chat without mutating the source |
|
|
66
|
+
| `/model` | List vendors, then vendor-scoped models and pricing |
|
|
67
|
+
| `/footer [compact|expanded|field on|off]` | Configure telemetry visibility |
|
|
66
68
|
| `/cost` | Show usage and billing data |
|
|
67
69
|
| `/config` | View and edit configuration |
|
|
68
70
|
| `/help` | Show all slash-command help |
|
|
69
71
|
|
|
70
|
-
> **Note:** `chat`, `login`, `
|
|
72
|
+
> **Note:** `chat`, `login`, `model`, `footer`, `cost`, and `config` are REPL slash-commands (prefixed with `/`), not top-level argv subcommands. The CLI is single-chat: fanout/swarm commands are hidden and disabled. Run `msapling --help` to see the argv interface.
|
|
71
73
|
|
|
72
74
|
See `packages/cli/src/commands/index.ts` for the canonical slash-command list.
|
|
73
75
|
|
|
@@ -83,7 +85,7 @@ MSapling started as a multi-chat browser workspace: multiple AI chats, many mode
|
|
|
83
85
|
|
|
84
86
|
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.
|
|
85
87
|
|
|
86
|
-
The CLI
|
|
88
|
+
The CLI uses the same backend state through a fixed project named `CLI` and one active chat at a time. It should be fast, low-resource, and useful without duplicating the backend.
|
|
87
89
|
|
|
88
90
|
## Architecture
|
|
89
91
|
|
|
@@ -96,7 +98,7 @@ CLI /
|
|
|
96
98
|
The CLI should:
|
|
97
99
|
|
|
98
100
|
- authenticate with the backend
|
|
99
|
-
- read
|
|
101
|
+
- read the fixed `CLI` project and active chat from the backend
|
|
100
102
|
- stream chat responses from `/api/chat/message`
|
|
101
103
|
- display backend usage and quota data
|
|
102
104
|
- respect backend stream locks
|
|
@@ -105,7 +107,8 @@ The CLI should:
|
|
|
105
107
|
|
|
106
108
|
The CLI should not:
|
|
107
109
|
|
|
108
|
-
- invent separate chat state
|
|
110
|
+
- invent separate chat state or switch arbitrary web chats
|
|
111
|
+
- expose multi-chat/swarm fanout commands
|
|
109
112
|
- compute billing locally
|
|
110
113
|
- simulate MDrive state
|
|
111
114
|
- bypass backend locks
|