turbollm 1.11.1 → 1.11.6

package/README.md

@@ -291,6 +291,13 @@ the detail:
   in chat (name, preferences, hardware) using your own loaded model, and carries them into future
   new conversations. Nothing leaves your device; the full fact list is reviewable and deletable
   from Settings → Memory, and turning the toggle off stops new chats from seeing it immediately.
+- **Turbo Link** *(experimental, off by default)* — link a second machine running TurboLLM
+  with one pasted link string and use its models as if they were local: they appear in the chat
+  model picker (grouped by machine), in `/v1/models` and in `launch --model`, and Models,
+  Downloads and Engines merge both machines' rows into one list. You grant an explicit capability
+  set per link — use models only, run a server, or full control — optionally pinned to specific
+  models, and revocable at any time from the host. Not yet verified against a real two-machine
+  setup, so it stays behind Settings → Experimental.
 - **Thinking-budget control** — a graduated slider, not just on/off: cap reasoning to a specific
   token count, disable it entirely, or leave it unlimited. Works in Chat and Code alike.
 - **Reasoning-effort control** for models whose own chat template supports it (e.g. Qwen3.8) —
@@ -326,10 +333,12 @@ there. Entirely local; nothing leaves your machine.
   MCP-compatible tool (Claude Desktop, Cursor, Windsurf, Cline, Claude Code, and more) can
   delegate a real coding task to Code, not just chat completions. Setup snippets for any host are
   in the Developer tab.
-- **Or run Claude Code itself, inside Code** — set Settings → Code agent to `claude` and a session
+- **Or run Claude Code, `pi` or `opencode` itself, inside Code** — set Settings → Code agent and a session
   opens the real CLI in a full-screen terminal, on your local model, in your project folder. The
   model picker, context ring, thinking-budget slider and stats row stay right where they are: the
-  CLI replaces the transcript, not the controls. It starts in the mode you picked (auto / plan /
+  CLI replaces the transcript, not the controls. Any of the three not installed yet is shown
+  with an Install button rather than failing when you open the session, and a CLI launched this
+  way sees only your local models — never your cloud API keys. It starts in the mode you picked (auto / plan /
   ask), the thinking budget applies live with no restart, switching models keeps your scrollback,
   and the conversation survives a restart of TurboLLM. The terminal backend is an optional native
   component — if it can't be built for your platform it's skipped (TurboLLM installs and runs
@@ -353,7 +362,7 @@ there. Entirely local; nothing leaves your machine.
 </details>
 
 <details>
-<summary><strong>🔌 APIs &amp; integrations — OpenAI + Anthropic, plus a model-loading gateway</strong></summary>
+<summary><strong>🔌 APIs &amp; integrations — OpenAI + Anthropic, a model-loading gateway, and a stateful chat API</strong></summary>
 
 <br/>
 
@@ -373,6 +382,17 @@ curl http://127.0.0.1:6996/v1/chat/completions \
   Claude Code below. No other local host offers this.
 - **Structured output** — constrain any response to a **GBNF grammar** (or JSON shape).
 - **API-key auth** you can require when sharing over a LAN (Settings → Network & sharing).
+- **A stateful External Chat API** (**Experimental — manual setup, no onboarding UI yet**),
+  `/api/ext/v1`, for building a real chat product instead of the gateway's stateless
+  send-full-history-every-call model — persistence, history, message editing, and resumable
+  streaming generation are handled for you. Off by default; using it today needs two manual
+  `config.json` edits — a key with an explicit, non-`local` `tenant` field (the local tenant, this
+  install's own desktop UI data, is never reachable through this API), and a configured
+  `chatStore` adapter (the SQLite default only ever serves the `local` tenant). A generated
+  OpenAPI spec, a TypeScript client, and a working Postgres adapter example ship with it. The
+  daemon logs a warning at startup while it's enabled — a remote tenant's generations currently
+  inherit this install's own tool permissions, not an independent trust boundary of their own.
+  [Full guide](https://turbollm.dev/docs/api/external).
 
 **The gateway loads models for you.** Most local hosts make you load a model first, then call it.
 TurboLLM's gateway reads the `model` field of any incoming request, **fuzzy-matches it to your

package/dist/{chunk-BWZ74SDA.js → chunk-YWVYF446.js}

@@ -25,10 +25,7 @@ function resolveExecutable(command, env = process.env, platform = process.platfo
   if (!command) return null;
   const win32 = platform === "win32";
   const exts = win32 ? (env.PATHEXT ?? ".COM;.EXE;.BAT;.CMD").split(";").filter(Boolean).map((e) => e.toLowerCase()) : [""];
-  const candidates = (base) => (
-    // An explicit extension is honoured as-is; only an extension-less command gets PATHEXT applied.
-    extname(base) ? [base] : [base, ...exts.map((e) => base + e)]
-  );
+  const candidates = (base) => extname(base) ? [base] : win32 ? exts.map((e) => base + e) : [base];
   if (isAbsolute(command) || command.startsWith("./") || command.startsWith(".\\")) {
     return candidates(command).find(isExecutableFile) ?? null;
   }