@mtreeai/msapling-cli 2.3.6-beta.51 → 2.3.6-beta.52

package/README.md

@@ -63,7 +63,10 @@ Once the REPL is running, type `/help` to see all available slash commands. Comm
 | `/chat <message>` | Send a message and stream a response |
 | `/chat new <title>` | Create a chat inside the fixed CLI project |
 | `/chat import <chat_id>` | Copy another owned chat into a new CLI chat without mutating the source |
-| `/model` | List vendors, then vendor-scoped models and pricing |
+| `/model` | Open the loopback visual catalog (complete LAB catalog remotely; direct provider catalog standalone) |
+| `/model --terminal` | Use the provider-first terminal selector instead |
+| `/keys add <provider>` | Enter a BYOK key through hidden terminal input or the one-time local browser prompt |
+| `/keys use <provider> [base_url]` | Select OpenRouter or an OpenAI-compatible provider in standalone mode |
 | `/footer [compact|expanded|field on|off]` | Configure telemetry visibility |
 | `/cost` | Show usage and billing data |
 | `/config` | View and edit configuration |
@@ -77,7 +80,7 @@ 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.
+The installed CLI has explicit remote and standalone profiles. In remote mode, MSapling's backend is the source of truth for auth, projects, chats, model routing, usage, billing, MDrive, locks, and audit data. In `--local` mode, model calls, provider keys, transcripts, tools, and project settings remain local and LAB is not contacted for turns.
 
 ## Product Direction