abstractframework 0.11.4__tar.gz → 0.11.6__tar.gz

{abstractframework-0.11.4 → abstractframework-0.11.6}/CHANGELOG.md

@@ -2,6 +2,62 @@
 
 All notable changes to AbstractFramework will be documented in this file.
 
+## [0.11.6] - 2026-10-18
+
+Windows fixes: a fresh Windows install works from the one-liner, with its local engines, the
+console's downloads, the desktop Assistant and the command-line tools; image routes can use an
+OpenAI-compatible endpoint that serves an image model. Pins **abstractcore 2.26.3**,
+**abstractgateway 0.15.3**, **abstractassistant 0.14.1**, **AbstractRuntime 0.10.3** and
+**abstractvision 0.3.34**; every other package is unchanged from 0.11.5.
+
+### Fixed
+
+- **First install from the one-liner**: `powershell -ExecutionPolicy ByPass -c "irm https://abstractframework.ai/install.ps1 | iex"` completes on Windows PowerShell 5.1. A first install no longer stops at step [4] with `ERROR: No tools installed`. The installer runs under PowerShell's default error handling whatever the calling session sets, and gives the caller's setting back when it ends.
+- **Gateway pointer**: the installer updates `%USERPROFILE%\.abstractframework\gateway.json` when the gateway has already written it, instead of warning that it could not write the pointer.
+- **Browser apps step**: right after the health check, the installer gives a gateway that is still finishing its start (including `"status": "starting"`) up to about 45 seconds before it defers the app upgrades to the next start.
+- **Re-runs**: the installer recognizes its own background gateway when uv's launcher starts the interpreter through the virtual environment's `python.exe`, keeps it running, and no longer reports it as started by hand.
+- **Local engines on Windows (AbstractGateway 0.15.3)**: llama.cpp and Hugging Face (transformers) show as ready on a Windows gpu install instead of "Not for this computer". vLLM explains that it runs in WSL2 or on a Linux machine.
+- **Workspace files on Windows (AbstractGateway 0.15.3)**: opening or downloading a file from a run's workspace works; Windows credential folders join the built-in protected folders.
+- **Command-line tools on Windows** (AbstractCore 2.26.3, AbstractGateway 0.15.3, AbstractVoice 0.15.1 and later, AbstractMusic 0.1.17): `abstractcore --status`, `abstractgateway network status`, `abstractvoice tts`, `abstractmusic --help` and the other commands no longer stop with `UnicodeEncodeError` when their output is piped or redirected.
+- **llama.cpp on processors without AVX-512**: llama.cpp's `cu130` Windows build is compiled with AVX-512; on a processor without it (most desktop Intel CPUs) it passed the installer's check and then ended the gateway's Python with an illegal instruction at its first GGUF model load. The installer now compares the instructions each build was compiled for with the processor's and tries `cu132` next (same CUDA 13 libraries, no AVX-512); `install.sh` puts the CPU build back on Linux in the same case. A re-run fixes an existing install.
+- **Hugging Face downloads on Windows (AbstractCore 2.26.3)**: downloads from the gateway console run to the end; they stopped a second after starting with "the Hugging Face download process exited 75" (for example faster-whisper `large-v3`, the default speech-to-text model). `abstractcore models download huggingface <repo>` also completes in a cache that holds copies instead of symbolic links (Windows without Developer Mode).
+- **No flashing console windows (AbstractGateway 0.15.3)**: a gateway started at login no longer opens a console window for a moment each time it runs a program such as `nvidia-smi` for the GPU meter.
+- **Desktop Assistant on Windows (AbstractAssistant 0.14.1, AbstractGateway 0.15.3)**: opening the Assistant from the gateway console signs it in (its sign-in file was refused with "permissions are 0o666, not 0o600"), and it opens without an empty console window next to it.
+- **Stopped tools on Windows (AbstractCore 2.26.3)**: a command or browser tool that is stopped ends every process it started.
+- **Install summary on Windows** says that agents' shell commands are refused there (no command sandbox); [Install](docs/install.md#windows) lists what runs locally on Windows.
+
+- **Image routes on OpenAI-compatible endpoints (AbstractGateway 0.15.3, AbstractVision 0.3.34, AbstractRuntime 0.10.3)**: an endpoint connection that serves an image model (for example a relay with `gpt-image-2`) is offered for text-to-image and image edits in the consoles, and a route set to it runs on that endpoint.
+
+### Changed
+
+- CI runs the Windows install the way the one-liner does: a script block evaluated under `$ErrorActionPreference = 'Stop'`.
+
+## [0.11.5] - 2026-10-18
+
+Pins **AbstractGateway 0.15.2** across the light, Apple and GPU profiles: the gateway stops browser apps
+left running by a previous gateway run and starts the installed version, at start and on every launch or
+update, and its systemd user unit stops its children with it. Pins **AbstractVoice 0.15.2**: read aloud
+speaks whole sentences in one language per reply, without a pause after the first words (0.15.1: the
+voice command-line tools write piped output on Windows). Other package pins are unchanged.
+
+Installer fix: an app left running by a previous gateway run no longer keeps an older version on its
+port across upgrades.
+
+- `install.sh` and `install.ps1` tell a leftover of a previous gateway run — an "external" copy whose
+  process runs a program under `<data dir>/apps/`, which only the gateway puts there — from a copy
+  started elsewhere. The leftover is stopped (its command line checked before each signal; SIGTERM,
+  then SIGKILL after 20 s) and the updated install is started with `abstractgateway apps launch`;
+  the summary's Apps line says `leftover of a previous gateway run (<version>, pid <pid>) stopped;
+  <app> <version> started`. A copy that is not provably this install's is left alone and listed as
+  `a copy not started by this gateway` with what was checked, never as "started outside the gateway".
+- The summary's closing line for app failures now says what to do for the apps (run the command on
+  their line, then `abstractgateway apps list`), instead of advising a re-run once the network has
+  caught up. See [Upgrade the apps](docs/install.md#upgrade-the-apps).
+- Who is affected: anyone upgrading with the one-line installers whose gateway runs the browser apps;
+  most visibly Linux servers where the gateway runs as a `systemd --user` service. Gateways from
+  0.15.2 on stop such leftovers themselves at start and on every launch or update; the installer's
+  stop covers earlier gateways.
+
 ## [0.11.4] - 2026-10-17
 
 Installer fix: upgrades keep the browser apps on the release. Package pins are unchanged from 0.11.3

{abstractframework-0.11.4/abstractframework.egg-info → abstractframework-0.11.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstractframework
-Version: 0.11.4
+Version: 0.11.6
 Summary: Unified installer and documentation hub for the AbstractFramework ecosystem
 Author-email: Laurent-Philippe Albou <contact@abstractframework.ai>
 License: MIT
@@ -23,24 +23,24 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: abstractgateway==0.15.1
-Requires-Dist: abstractassistant==0.14.0
-Requires-Dist: abstractcore==2.26.0
-Requires-Dist: AbstractRuntime==0.10.2
+Requires-Dist: abstractgateway==0.15.3
+Requires-Dist: abstractassistant==0.14.1
+Requires-Dist: abstractcore==2.26.3
+Requires-Dist: AbstractRuntime==0.10.3
 Requires-Dist: abstractagent==0.3.19
 Requires-Dist: abstractskill==0.3.0
 Requires-Dist: AbstractMemory==0.3.0
 Requires-Dist: abstractsemantics==0.0.5
-Requires-Dist: abstractvoice==0.15.0
-Requires-Dist: abstractvision==0.3.33
-Requires-Dist: abstractmusic==0.1.16
+Requires-Dist: abstractvoice==0.15.2
+Requires-Dist: abstractvision==0.3.34
+Requires-Dist: abstractmusic==0.1.17
 Requires-Dist: abstract3d==0.3.2
 Provides-Extra: apple
-Requires-Dist: abstractgateway[apple]==0.15.1; extra == "apple"
-Requires-Dist: abstractassistant[apple]==0.14.0; platform_system == "Darwin" and extra == "apple"
+Requires-Dist: abstractgateway[apple]==0.15.3; extra == "apple"
+Requires-Dist: abstractassistant[apple]==0.14.1; platform_system == "Darwin" and extra == "apple"
 Provides-Extra: gpu
-Requires-Dist: abstractgateway[gpu]==0.15.1; extra == "gpu"
-Requires-Dist: abstractassistant[gpu]==0.14.0; extra == "gpu"
+Requires-Dist: abstractgateway[gpu]==0.15.3; extra == "gpu"
+Requires-Dist: abstractassistant[gpu]==0.14.1; extra == "gpu"
 Dynamic: license-file
 
 # AbstractFramework
@@ -221,7 +221,7 @@ abstractgateway-console --gateway-url http://127.0.0.1:8080 --token <admin token
 ```
 
 Container images are published for the gateway and the AbstractCore server:
-`ghcr.io/lpalbou/abstractgateway:0.15.1` and `ghcr.io/lpalbou/abstractcore-server:2.26.0`.
+`ghcr.io/lpalbou/abstractgateway:0.15.3` and `ghcr.io/lpalbou/abstractcore-server:2.26.3`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -383,17 +383,17 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.15.1 |
-| PyPI | `abstractassistant` | 0.14.0 |
-| PyPI | `abstractcore` | 2.26.0 |
-| PyPI | `AbstractRuntime` | 0.10.2 |
+| PyPI | `abstractgateway` | 0.15.3 |
+| PyPI | `abstractassistant` | 0.14.1 |
+| PyPI | `abstractcore` | 2.26.3 |
+| PyPI | `AbstractRuntime` | 0.10.3 |
 | PyPI | `abstractagent` | 0.3.19 |
 | PyPI | `abstractskill` | 0.3.0 |
 | PyPI | `AbstractMemory` | 0.3.0 |
 | PyPI | `abstractsemantics` | 0.0.5 |
-| PyPI | `abstractvoice` | 0.15.0 |
-| PyPI | `abstractvision` | 0.3.33 |
-| PyPI | `abstractmusic` | 0.1.16 |
+| PyPI | `abstractvoice` | 0.15.2 |
+| PyPI | `abstractvision` | 0.3.34 |
+| PyPI | `abstractmusic` | 0.1.17 |
 | PyPI | `abstract3d` | 0.3.2 |
 | npm | `@abstractframework/flow` | 0.10.0 |
 | npm | `@abstractframework/code` | 0.11.2 |
@@ -404,8 +404,8 @@ and tested together.
 | crates.io | `abstractgateway-console` | 0.16.0 |
 | crates.io | `abstractcore-console` | 0.8.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.15.1 (`gpu-latest` / `<version>-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.26.0 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.15.3 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.26.3 |
 
 `abstract3d` (pinned above) comes with AbstractCore in every profile. The optional add-on that is
 not part of any profile installs separately: `pip install abstractcamera` (0.2.1). `abstractskill` (pinned above)

{abstractframework-0.11.4 → abstractframework-0.11.6}/README.md

@@ -176,7 +176,7 @@ abstractgateway-console --gateway-url http://127.0.0.1:8080 --token <admin token
 ```
 
 Container images are published for the gateway and the AbstractCore server:
-`ghcr.io/lpalbou/abstractgateway:0.15.1` and `ghcr.io/lpalbou/abstractcore-server:2.26.0`.
+`ghcr.io/lpalbou/abstractgateway:0.15.3` and `ghcr.io/lpalbou/abstractcore-server:2.26.3`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -338,17 +338,17 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.15.1 |
-| PyPI | `abstractassistant` | 0.14.0 |
-| PyPI | `abstractcore` | 2.26.0 |
-| PyPI | `AbstractRuntime` | 0.10.2 |
+| PyPI | `abstractgateway` | 0.15.3 |
+| PyPI | `abstractassistant` | 0.14.1 |
+| PyPI | `abstractcore` | 2.26.3 |
+| PyPI | `AbstractRuntime` | 0.10.3 |
 | PyPI | `abstractagent` | 0.3.19 |
 | PyPI | `abstractskill` | 0.3.0 |
 | PyPI | `AbstractMemory` | 0.3.0 |
 | PyPI | `abstractsemantics` | 0.0.5 |
-| PyPI | `abstractvoice` | 0.15.0 |
-| PyPI | `abstractvision` | 0.3.33 |
-| PyPI | `abstractmusic` | 0.1.16 |
+| PyPI | `abstractvoice` | 0.15.2 |
+| PyPI | `abstractvision` | 0.3.34 |
+| PyPI | `abstractmusic` | 0.1.17 |
 | PyPI | `abstract3d` | 0.3.2 |
 | npm | `@abstractframework/flow` | 0.10.0 |
 | npm | `@abstractframework/code` | 0.11.2 |
@@ -359,8 +359,8 @@ and tested together.
 | crates.io | `abstractgateway-console` | 0.16.0 |
 | crates.io | `abstractcore-console` | 0.8.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.15.1 (`gpu-latest` / `<version>-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.26.0 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.15.3 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.26.3 |
 
 `abstract3d` (pinned above) comes with AbstractCore in every profile. The optional add-on that is
 not part of any profile installs separately: `pip install abstractcamera` (0.2.1). `abstractskill` (pinned above)

{abstractframework-0.11.4 → abstractframework-0.11.6}/abstractframework/__init__.py

@@ -10,23 +10,23 @@ Most implementation functionality still lives in component projects.
 
 from __future__ import annotations
 
-__version__ = "0.11.4"
+__version__ = "0.11.6"
 __author__ = "Laurent-Philippe Albou"
 __license__ = "MIT"
 
 RELEASE_VERSIONS: dict[str, str] = {
-    "abstractcore": "2.26.0",
-    "abstractruntime": "0.10.2",
+    "abstractcore": "2.26.3",
+    "abstractruntime": "0.10.3",
     "abstractagent": "0.3.19",
-    "abstractgateway": "0.15.1",
+    "abstractgateway": "0.15.3",
     "abstractskill": "0.3.0",
     "abstractmemory": "0.3.0",
     "abstractsemantics": "0.0.5",
-    "abstractvoice": "0.15.0",
-    "abstractvision": "0.3.33",
-    "abstractmusic": "0.1.16",
+    "abstractvoice": "0.15.2",
+    "abstractvision": "0.3.34",
+    "abstractmusic": "0.1.17",
     "abstract3d": "0.3.2",
-    "abstractassistant": "0.14.0",
+    "abstractassistant": "0.14.1",
 }
 
 PACKAGE_DISTRIBUTIONS: dict[str, str] = {

{abstractframework-0.11.4 → abstractframework-0.11.6/abstractframework.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstractframework
-Version: 0.11.4
+Version: 0.11.6
 Summary: Unified installer and documentation hub for the AbstractFramework ecosystem
 Author-email: Laurent-Philippe Albou <contact@abstractframework.ai>
 License: MIT
@@ -23,24 +23,24 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: abstractgateway==0.15.1
-Requires-Dist: abstractassistant==0.14.0
-Requires-Dist: abstractcore==2.26.0
-Requires-Dist: AbstractRuntime==0.10.2
+Requires-Dist: abstractgateway==0.15.3
+Requires-Dist: abstractassistant==0.14.1
+Requires-Dist: abstractcore==2.26.3
+Requires-Dist: AbstractRuntime==0.10.3
 Requires-Dist: abstractagent==0.3.19
 Requires-Dist: abstractskill==0.3.0
 Requires-Dist: AbstractMemory==0.3.0
 Requires-Dist: abstractsemantics==0.0.5
-Requires-Dist: abstractvoice==0.15.0
-Requires-Dist: abstractvision==0.3.33
-Requires-Dist: abstractmusic==0.1.16
+Requires-Dist: abstractvoice==0.15.2
+Requires-Dist: abstractvision==0.3.34
+Requires-Dist: abstractmusic==0.1.17
 Requires-Dist: abstract3d==0.3.2
 Provides-Extra: apple
-Requires-Dist: abstractgateway[apple]==0.15.1; extra == "apple"
-Requires-Dist: abstractassistant[apple]==0.14.0; platform_system == "Darwin" and extra == "apple"
+Requires-Dist: abstractgateway[apple]==0.15.3; extra == "apple"
+Requires-Dist: abstractassistant[apple]==0.14.1; platform_system == "Darwin" and extra == "apple"
 Provides-Extra: gpu
-Requires-Dist: abstractgateway[gpu]==0.15.1; extra == "gpu"
-Requires-Dist: abstractassistant[gpu]==0.14.0; extra == "gpu"
+Requires-Dist: abstractgateway[gpu]==0.15.3; extra == "gpu"
+Requires-Dist: abstractassistant[gpu]==0.14.1; extra == "gpu"
 Dynamic: license-file
 
 # AbstractFramework
@@ -221,7 +221,7 @@ abstractgateway-console --gateway-url http://127.0.0.1:8080 --token <admin token
 ```
 
 Container images are published for the gateway and the AbstractCore server:
-`ghcr.io/lpalbou/abstractgateway:0.15.1` and `ghcr.io/lpalbou/abstractcore-server:2.26.0`.
+`ghcr.io/lpalbou/abstractgateway:0.15.3` and `ghcr.io/lpalbou/abstractcore-server:2.26.3`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -383,17 +383,17 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.15.1 |
-| PyPI | `abstractassistant` | 0.14.0 |
-| PyPI | `abstractcore` | 2.26.0 |
-| PyPI | `AbstractRuntime` | 0.10.2 |
+| PyPI | `abstractgateway` | 0.15.3 |
+| PyPI | `abstractassistant` | 0.14.1 |
+| PyPI | `abstractcore` | 2.26.3 |
+| PyPI | `AbstractRuntime` | 0.10.3 |
 | PyPI | `abstractagent` | 0.3.19 |
 | PyPI | `abstractskill` | 0.3.0 |
 | PyPI | `AbstractMemory` | 0.3.0 |
 | PyPI | `abstractsemantics` | 0.0.5 |
-| PyPI | `abstractvoice` | 0.15.0 |
-| PyPI | `abstractvision` | 0.3.33 |
-| PyPI | `abstractmusic` | 0.1.16 |
+| PyPI | `abstractvoice` | 0.15.2 |
+| PyPI | `abstractvision` | 0.3.34 |
+| PyPI | `abstractmusic` | 0.1.17 |
 | PyPI | `abstract3d` | 0.3.2 |
 | npm | `@abstractframework/flow` | 0.10.0 |
 | npm | `@abstractframework/code` | 0.11.2 |
@@ -404,8 +404,8 @@ and tested together.
 | crates.io | `abstractgateway-console` | 0.16.0 |
 | crates.io | `abstractcore-console` | 0.8.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.15.1 (`gpu-latest` / `<version>-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.26.0 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.15.3 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.26.3 |
 
 `abstract3d` (pinned above) comes with AbstractCore in every profile. The optional add-on that is
 not part of any profile installs separately: `pip install abstractcamera` (0.2.1). `abstractskill` (pinned above)

abstractframework-0.11.6/abstractframework.egg-info/requires.txt

@@ -0,0 +1,22 @@
+abstractgateway==0.15.3
+abstractassistant==0.14.1
+abstractcore==2.26.3
+AbstractRuntime==0.10.3
+abstractagent==0.3.19
+abstractskill==0.3.0
+AbstractMemory==0.3.0
+abstractsemantics==0.0.5
+abstractvoice==0.15.2
+abstractvision==0.3.34
+abstractmusic==0.1.17
+abstract3d==0.3.2
+
+[apple]
+abstractgateway[apple]==0.15.3
+
+[apple:platform_system == "Darwin"]
+abstractassistant[apple]==0.14.1
+
+[gpu]
+abstractgateway[gpu]==0.15.3
+abstractassistant[gpu]==0.14.1

{abstractframework-0.11.4 → abstractframework-0.11.6}/docs/api.md

@@ -55,14 +55,14 @@ The response type returned by `llm.generate(...)`.
 
 ### `__version__`
 
-The meta-package version (`0.11.4` for this release).
+The meta-package version (`0.11.6` for this release).
 
 ### `RELEASE_VERSIONS`
 
-Dictionary mapping each ecosystem package name to the pinned version for this release. In 0.11.4:
-`abstractcore` 2.26.0, `abstractruntime` 0.10.2, `abstractagent` 0.3.19, `abstractgateway` 0.15.1,
-`abstractskill` 0.3.0, `abstractmemory` 0.3.0, `abstractsemantics` 0.0.5, `abstractvoice` 0.15.0, `abstractvision` 0.3.33,
-`abstractmusic` 0.1.16, `abstract3d` 0.3.2, `abstractassistant` 0.14.0.
+Dictionary mapping each ecosystem package name to the pinned version for this release. In 0.11.6:
+`abstractcore` 2.26.3, `abstractruntime` 0.10.3, `abstractagent` 0.3.19, `abstractgateway` 0.15.3,
+`abstractskill` 0.3.0, `abstractmemory` 0.3.0, `abstractsemantics` 0.0.5, `abstractvoice` 0.15.2, `abstractvision` 0.3.34,
+`abstractmusic` 0.1.17, `abstract3d` 0.3.2, `abstractassistant` 0.14.1.
 
 ### `PACKAGE_DISTRIBUTIONS`
 

{abstractframework-0.11.4 → abstractframework-0.11.6}/docs/install.md

@@ -80,6 +80,23 @@ browser. It asks whether to start AbstractFramework at sign-in, like the Mac and
 Enter = yes, no answer within 25 seconds (or no console to ask on) leaves it off on a first install.
 `-NoService` leaves it off and asks nothing.
 
+What runs locally on Windows with the gpu profile (x86_64, NVIDIA):
+
+| Engine | On Windows |
+|---|---|
+| llama.cpp (GGUF models, in the gateway) | Yes: the installer adds llama.cpp's prebuilt CUDA, Vulkan or CPU build. |
+| Hugging Face Transformers | Yes, on PyTorch's CUDA build. |
+| Diffusers (image generation), faster-whisper (speech to text), sentence-transformers | Yes. |
+| Ollama, LM Studio | Yes: install them from the console's **Local engines** page (or `-WithOllama`, `-WithLmStudio`). |
+| vLLM | No native Windows build: run it in WSL2 or on a Linux machine, and point the gateway at that server. |
+| MLX | Apple silicon Macs only. |
+
+Agents' shell commands need a sandbox, and Windows has none that the gateway supports, so the
+gateway refuses those commands on Windows; every other tool works. AbstractGateway's
+[security guide](https://github.com/lpalbou/AbstractGateway/blob/main/docs/security.md) explains
+`abstractgateway serve --unsandboxed-commands`, which runs them with your account's own file
+access, for a gateway you start yourself.
+
 ## If something goes wrong
 
 The installer stops at the first problem, says what happened in plain words, and says what to do.
@@ -113,7 +130,7 @@ where it stopped.
 ### Right after a release
 
 For a few minutes after a release, some of PyPI's mirrors can still serve a package list without
-the new versions. uv then answers `there is no version of abstractgateway==0.8.1` even though the
+the new versions. uv then answers `there is no version of abstractgateway==0.15.3` even though the
 release is published. The installer (install.sh and install.ps1; the **Update** action of the
 consoles and the menu-bar icon runs install.sh on macOS and Linux, and gives the install.ps1 line to
 paste on Windows) treats that as a delay:
@@ -369,12 +386,26 @@ update restarts it on the new version. The summary's **Apps** line lists each ap
 that could not be updated is listed in red with the command to retry, and the installer exits 1. A
 fresh install installs no app: the console's **Apps** page installs them.
 
-An app's port may be held by a copy the gateway did not start: a leftover of a gateway that died
-hard, or an app run by hand with `npx`. The gateway lists that copy as *external* and cannot stop or
-restart it, so the gateway's own install is updated and the **Apps** line says `RUNNING: a copy
-started outside the gateway, <version> on port <port> (pid <pid>)`; when that copy is not at this
-release's version, the summary shows it in red with the pid to stop (`kill <pid>`, then
-`abstractgateway apps launch <app>`).
+An app's port may be held by a copy this gateway did not start. The gateway's own install is
+updated all the same, and what happens to the copy depends on what it is:
+
+- **A leftover of a previous gateway run** — the process runs a program under `<data dir>/apps/`,
+  which only the gateway puts there (an app that outlived a stop or restart of the gateway, for
+  example on a Linux server, and kept serving an older version). The installer stops it (its command
+  line is checked again before each signal; SIGTERM, then SIGKILL after 20 s) and starts the updated
+  install in its place with `abstractgateway apps launch <app>`; the **Apps** line says
+  `leftover of a previous gateway run (<version>, pid <pid>) stopped; <app> <version> started`. If
+  the leftover could not be stopped or the app did not start, the summary says so in red with the
+  command to run. Gateways from 0.15.2 on do this themselves at every start and on every
+  `apps launch` or `apps update`, so the installer's stop is only needed with an older gateway.
+- **A copy not started by this gateway** — anything else (an app run by hand with `npx`, a checkout,
+  a process this system cannot inspect). It is left alone: the **Apps** line says `RUNNING: a copy
+  not started by this gateway, <version> on port <port> (pid <pid>)` and, when that copy is not at
+  this release's version, the summary shows it in red with what was checked and the pid to stop,
+  then `abstractgateway apps launch <app>`.
+
+The summary's last line then points at the apps (`What to do for the apps: run the command given on
+their line above, then check them with: abstractgateway apps list …`), not at a re-run.
 
 When no gateway answers (`--no-start` while the gateway is stopped), the installer writes the
 release's versions to `<data dir>/apps-upgrade.pending` instead, and the gateway (0.11.1 and later)
@@ -399,7 +430,7 @@ The terminal console and an `abstractcode` built by the installer are upgraded b
 
 ```bash
 abstractgateway --version                    # the installed gateway
-uv tool list --show-version-specifiers       # the gateway uv tool and its pin ([required: ==0.15.1])
+uv tool list --show-version-specifiers       # the gateway uv tool and its pin ([required: ==0.15.3])
 abstractgateway-console --version            # the terminal console
 abstractcode --version                       # AbstractCode's terminal client
 abstractgateway apps list                    # the apps: installed and latest
@@ -475,10 +506,10 @@ The Mac package, the `.command` files and the one line all run the same script,
    login** switch counts), a first install leaves it off.
 3. Installs [uv](https://docs.astral.sh/uv/) when it is missing, then Python 3.12 through uv.
 4. Installs the gateway as an isolated uv tool, pinned to this release:
-   `uv tool install --python 3.12 "abstractgateway[<profile>,tray]==0.15.1"`, from prebuilt wheels
+   `uv tool install --python 3.12 "abstractgateway[<profile>,tray]==0.15.3"`, from prebuilt wheels
    only (see [No compiler needed](#no-compiler-needed)), and checks that the command starts
    (reinstalling it in place when it does not). Every profile also gets local voice,
-   `--with "abstractvoice[supertonic,stt]==0.15.0"` (the release's AbstractVoice): Supertonic
+   `--with "abstractvoice[supertonic,stt]==0.15.2"` (the release's AbstractVoice): Supertonic
    text-to-speech and Whisper speech-to-text, both on CPU (skipped on musl Linux and macOS before
    13, where no wheels exist; Windows ARM64 gets Supertonic only). If those packages do not install
    on a system (for example glibc older than 2.28), the gateway is installed without them and the
@@ -636,7 +667,7 @@ What to expect on a GPU of this size:
 - **Loaded image models are reused.** After **Load** in the console (or `POST /models/load`),
   image requests run on the loaded model, and an unload frees its memory.
 
-Not validated: vLLM (installed, never started a model here) and the Windows gpu setting.
+Not validated: vLLM (installed, never started a model here).
 
 ### GPU on Windows (NVIDIA)
 
@@ -646,7 +677,7 @@ capability, prints the stack it picks and why, and installs:
 
 | NVIDIA driver | PyTorch | llama.cpp builds tried, in order |
 |---|---|---|
-| 580 or newer, compute capability 7.5 or newer | CUDA 13 (`cu130`, about 1.9 GB) | `cu130`, Vulkan, CPU |
+| 580 or newer, compute capability 7.5 or newer | CUDA 13 (`cu130`, about 1.9 GB) | `cu130`, `cu132`, Vulkan, CPU |
 | 525 or newer | CUDA 12 (`cu126`, about 2.5 GB) | `cu125`, Vulkan, CPU |
 | older, or no working NVIDIA GPU | PyPI's CPU build | Vulkan, CPU |
 
@@ -657,13 +688,22 @@ It announces the big downloads before they start and shows uv's output as it hap
 AbstractCore loads it and reports GPU offload, and which device faster-whisper picks. A part that
 does not work is replaced by one that does: a CUDA install that fails is retried without llama.cpp,
 then with PyTorch's CPU build; a llama.cpp build that does not load (or reports no GPU offload) is
-replaced by the next one, and removed when none loads. The summary's `GPU stack:`, `PyTorch:`,
+replaced by the next one, and removed when none loads. A build is also replaced when it was compiled
+for CPU instructions your processor lacks: llama.cpp's `cu130` build uses AVX-512, which most desktop
+Intel processors do not have, so those computers get the `cu132` build. On a GPU newer than the
+build's CUDA architectures (RTX 50 series), the first model load takes a minute or two while the
+driver compiles the GPU code; later loads reuse it. The summary's `GPU stack:`, `PyTorch:`,
 `GGUF:` and `Whisper:` lines say what runs where, and why. vLLM (Linux only upstream) and
 stable-diffusion.cpp (a source build that needs an elevated MSVC install) are not part of the
-Windows gpu profile; Diffusers on PyTorch covers image and video generation.
+Windows gpu profile; Diffusers on PyTorch covers image generation. Local video generation runs on
+Apple silicon (MLX) only.
 
-The Windows gpu setting has not yet been validated on real NVIDIA hardware: the stack choice, the
-fallbacks and the wheel-only resolves are tested with simulated drivers (root backlog 0988).
+Validated on Windows 10 22H2 with an NVIDIA GeForce RTX 5060 Ti (compute capability 12.0, driver
+617) and an Intel Core i7-5820K (no AVX-512): PyTorch 2.14.1 `cu130` on the GPU; llama.cpp 0.3.35
+`cu132` with GPU offload answering a GGUF chat model; a Hugging Face (transformers) chat model on
+CUDA; Diffusers text-to-image (`stabilityai/sd-turbo`, fp16 on CUDA); Supertonic text-to-speech;
+and faster-whisper `large-v3` speech-to-text on CUDA. The
+stack choice and its fallbacks for older drivers are tested with simulated drivers.
 
 ### Compiled extras
 
@@ -820,7 +860,7 @@ instead of starting a browser.
 ```bash
 curl -LsSf https://astral.sh/uv/install.sh | sh             # Windows: irm https://astral.sh/uv/install.ps1 | iex
 uv python install 3.12
-uv tool install --python 3.12 "abstractgateway[tray]==0.15.1"    # [apple,tray] or [gpu,tray] for local engines
+uv tool install --python 3.12 "abstractgateway[tray]==0.15.3"    # [apple,tray] or [gpu,tray] for local engines
                        # (add --with and --overrides as shown by `install.sh --print` to avoid compiling)
 uv tool update-shell                                          # puts ~/.local/bin on PATH; open a new terminal
 abstractgateway service install --port 8080                   # or: abstractgateway serve
@@ -954,10 +994,10 @@ Python 3.11 to 3.13), but it gets PyPI's CPU-only PyTorch and no llama.cpp: use
 installer, which adds PyTorch's CUDA build and llama.cpp's prebuilt GPU build
 ([GPU on Windows](#gpu-on-windows-nvidia)).
 
-`abstractframework` 0.11.4 pins `abstractgateway==0.15.1`, `abstractassistant==0.14.0`,
-`abstractcore==2.26.0`, `AbstractRuntime==0.10.2`, `abstractagent==0.3.19`, `abstractskill==0.3.0`,
-`AbstractMemory==0.3.0`, `abstractsemantics==0.0.5`, `abstractvoice==0.15.0`,
-`abstractvision==0.3.33`, `abstractmusic==0.1.16` and `abstract3d==0.3.2`. The `apple` and `gpu` extras select
+`abstractframework` 0.11.6 pins `abstractgateway==0.15.3`, `abstractassistant==0.14.1`,
+`abstractcore==2.26.3`, `AbstractRuntime==0.10.3`, `abstractagent==0.3.19`, `abstractskill==0.3.0`,
+`AbstractMemory==0.3.0`, `abstractsemantics==0.0.5`, `abstractvoice==0.15.2`,
+`abstractvision==0.3.34`, `abstractmusic==0.1.17` and `abstract3d==0.3.2`. The `apple` and `gpu` extras select
 `abstractgateway[apple|gpu]` and `abstractassistant[apple|gpu]` at the same versions
 (`abstractassistant[apple]` is installed on macOS only). `abstractframework doctor` reports any
 installed package whose version differs from these pins.
@@ -1046,7 +1086,7 @@ Run or install them next to the Python stack:
 | Tool | Command | Version released with 0.11.0 |
 |---|---|---|
 | Gateway web console | built into `abstractgateway`: open the link `abstractgateway serve` prints (`http://127.0.0.1:8080/console#claim=…`) | 0.14.0 |
-| Core web console | built into `abstractcore`: open the link `abstractcore serve` prints (`http://127.0.0.1:8000/console#claim=…`) | 2.26.0 |
+| Core web console | built into `abstractcore`: open the link `abstractcore serve` prints (`http://127.0.0.1:8000/console#claim=…`) | 2.26.3 |
 | Core terminal console | `cargo install abstractcore-console` (Rust 1.87+), then `abstractcore-console` (uses the `abstractcore` command). The installers do not build it: it is the console of a standalone `abstractcore serve`, and the gateway's terminal console already has its Models and Engines screens | 0.8.0 |
 | Gateway terminal console | built by the installer (`--no-console` skips it), or `cargo install abstractgateway-console` (Rust 1.87+); then `abstractgateway-console --gateway-url http://127.0.0.1:8080 --token <admin token>` | 0.16.0 |
 | Flow Editor | the console's **Apps** page (opens at `/apps/flow/`), or on its own: `npx @abstractframework/flow --gateway-url <url>` | 0.9.0 |
@@ -1097,7 +1137,7 @@ docker run \
   -v "$PWD/runtime:/data" \
   -e ABSTRACTGATEWAY_DATA_DIR=/data \
   -e ABSTRACTGATEWAY_USER_AUTH=1 \
-  ghcr.io/lpalbou/abstractgateway:0.15.1
+  ghcr.io/lpalbou/abstractgateway:0.15.3
 ```
 
 This is the Light container: full framework capabilities through remote/endpoint inference, without
@@ -1105,7 +1145,7 @@ local MLX/CUDA stacks. On first start it creates `default/admin` and writes the
 `runtime/auth/bootstrap-admin-token`. Use `ghcr.io/lpalbou/abstractgateway:gpu-latest` only on an
 NVIDIA host when you explicitly want the local GPU profile (pinned tags are `<version>-gpu`, published on a best-effort basis; this image is
 experimental). The AbstractCore OpenAI-compatible server is also published as
-`ghcr.io/lpalbou/abstractcore-server:2.26.0`.
+`ghcr.io/lpalbou/abstractcore-server:2.26.3`.
 
 ## How installs are designed
 

{abstractframework-0.11.4 → abstractframework-0.11.6}/docs/troubleshooting.md

@@ -81,6 +81,21 @@ run the installer again: it continues where it stopped.
 - **Fix**: paste the one-liner from [Install](install.md#windows), which runs a command rather than
   a script file, or ask your administrator.
 
+### Windows: the installer stops at `[4] AbstractGateway` with `ERROR: No tools installed`
+
+- **Cause**: the installer of AbstractFramework 0.11.3 stopped when it ran through the one-liner
+  on Windows PowerShell 5.1 and found no uv tool installed yet.
+- **Fix**: paste the one-liner from [Install](install.md#windows) again. It always fetches the
+  current installer, which resumes from the uv and Python already in place.
+- **Verify**: `abstractgateway --version` in a new terminal.
+
+### Windows: console windows flash on the desktop every few seconds
+
+- **Cause**: an AbstractGateway older than 0.15.3 started at login (through `pythonw.exe`) opens a
+  console window for each program it runs, such as `nvidia-smi` for the GPU meter.
+- **Fix**: paste the one-liner from [Install](install.md#windows) again, then sign out and back
+  in, or restart the gateway from its tray icon.
+
 ## Starting and signing in
 
 ### The browser page asks for a token, or the sign-in link expired
@@ -159,6 +174,14 @@ run the installer again: it continues where it stopped.
 
 ## Models and providers
 
+### Windows: a model download stops with "the Hugging Face download process exited 75"
+
+- **Cause**: with AbstractCore older than 2.26.3, Hugging Face downloads started from the gateway
+  console on Windows (for example faster-whisper `large-v3`, the default speech-to-text model)
+  stop a second after they start.
+- **Fix**: paste the one-liner from [Install](install.md#windows) again, then start the download
+  again from the console. Files that already finished are kept.
+
 ### Provider calls fail
 
 - **Check**: `abstractcore --status` for the persisted configuration, and whether a local server