abstractframework 0.6.2__tar.gz → 0.7.0__tar.gz

{abstractframework-0.6.2 → abstractframework-0.7.0}/CHANGELOG.md

@@ -4,6 +4,232 @@ All notable changes to AbstractFramework will be documented in this file.
 
 ## [Unreleased]
 
+## [0.7.0] - 2026-09-30
+
+Email for each user, and installer fixes. Pins: AbstractCore 2.20.1, AbstractRuntime 0.8.0,
+AbstractGateway 0.8.0 and AbstractAssistant 0.10.0; the terminal consoles are
+`abstractgateway-console` 0.12.0 and `abstractcore-console` 0.5.0, and the browser apps
+AbstractCode web 0.7.0 and AbstractObserver 0.3.0 (built on AbstractUIC ui-kit 0.2.0 and panel-chat
+0.1.21). Every other version is unchanged from 0.6.3.
+
+### Added
+
+- **Your own mailbox on the gateway.** Each user connects their own email account (IMAP/SMTP with a
+  password or app password, or OAuth2 for Google and Microsoft) in the web console (**Users → My
+  email**), the terminal console (`@` on the Users screen) or `PUT /api/gateway/me/email`. The
+  account is tested before it is saved, stored in the user's own data folder with its credentials
+  encrypted, and every connection verifies TLS. The mailbox is read-only. Each user sets a recipient
+  policy (allowlist or denylist of addresses and domains) and send limits (20 per hour and 100 per
+  day by default); every send passes them. AbstractCore on its own gets the same account, one per
+  install: `abstractcore email ...`, the core web console's **Email** tab and the core terminal
+  console's Email screen. See [Configuration](docs/configuration.md#email-accounts).
+  `abstractcore email connect --password-stdin` (and `--client-secret-stdin` for OAuth) reads the
+  secret from stdin, so it never appears on a command line (AbstractCore 2.20.1).
+- **Email automations.** The Assistant, the Observer and AbstractCode's browser client offer **When
+  an email arrives** (the `email.received@1` trigger: typed filters on sender, recipient, subject and
+  attachments; hourly batches by default for automations that run a model, never more often than
+  every 60 seconds; each message read once), **Email me the result**, and the recipients an
+  automation may email without asking (only you, by default). Inbound mail reaches the agent as
+  untrusted data in a fixed frame; an email-triggered automation never follows links from an email
+  (`fetch_url` and `browser_probe` ask) unless you name those tools. See
+  [Email automations](docs/automations.md#email-automations).
+- **Email notifications**, off until you turn them on in **My email → Notifications**: automation
+  results and failures (for automations set to email you), a run waiting for your approval, and
+  runs started with an email notice. Each notice is sent once from a durable outbox, through your
+  own account, to your registered address.
+- **Sign-in by email**: "Forgot your token?" and "Email me a sign-in code" on the gateway's sign-in
+  page for users with a connected account (single-use codes, 10-minute expiry).
+- **What administrators decide**: whether email, agent email tools and sign-in by email are
+  available, gateway-wide and per user. Agent email tools are off by default: an agent gets the
+  email tools only when an administrator made them available, the user's account is connected, and
+  the user turned them on. Administrators see a user's mailbox state, never mail.
+
+### Removed
+
+- The `ABSTRACT_EMAIL_*` environment variables, the email accounts file and the gateway's email
+  bridge. A gateway or an AbstractCore install that still has them imports that account once into
+  the new settings; afterwards each variable still set is named at startup with the setting that
+  replaced it.
+
+### Fixed
+
+- **One gateway per data directory when you re-run the installer.** A gateway of this install that
+  you started yourself (for example with the summary's Start line) is recognized: it listens on the
+  install's port and serves the same data directory, as its serve record
+  (`<data dir>/run/gateway-serve.json`) or its `--data-dir` says. `install.sh` and `install.ps1` now
+  keep that port and replace the gateway with their own start, instead of moving to the next port
+  and starting a second gateway on the same data. A gateway of this install started by hand on
+  another port is stopped too. The replacement starts the way the installer starts every gateway, so
+  it binds as the gateway's Network setting says (for example 127.0.0.1), not with the `--host` the
+  hand-started one was given. With `--no-start` (`-NoStart`, the console's Update) it keeps
+  running and the summary says a restart is due. A program that is not this install's gateway
+  keeps the port, as before.
+- **The installers signal only this install's gateway.** Before any stop, the process must belong
+  to your user, run `abstractgateway serve` and serve this data directory; the identity is checked
+  again right before the signal (and before a SIGKILL). A `gateway.pid` or serve record left behind
+  that names another program (a reused pid) is left alone and said so.
+- **Known limit on Windows with start at login on:** Windows does not tell the installer which
+  process the login item started, so a gateway of this data directory that you started yourself on
+  the install's port is taken for the login item and left running. Stop it and re-run the
+  installer to get the login item's gateway.
+- **A release published minutes earlier installs at once.** The installers pass
+  `--refresh-package` for `abstractgateway` and every package of the release matrix to
+  `uv tool install`, so uv asks PyPI again instead of using its cached index page (which could say
+  "no version of abstractgateway[gpu]==<pin>" until `uv cache clean abstractgateway`).
+
+### Changed
+
+- **Launch flags in the commands the installers print.** The summary's Start line and the
+  background start's command (the "same steps by hand" list) read
+  `abstractgateway serve --data-dir <data dir>` (plus `--host`/`--port` when the gateway has no
+  Network setting) instead of `ABSTRACTGATEWAY_DATA_DIR=... ABSTRACTGATEWAY_USER_AUTH=1 ...`; the
+  gateway starts with user auth on by itself. The installers themselves still pass the data dir to
+  the gateway commands they run (`network`, `service install`, `claim-url`) through
+  `ABSTRACTGATEWAY_DATA_DIR`. Gateways before 0.3 (`--pin`) keep the environment form.
+
+## [0.6.3] - 2026-09-29
+
+The `gpu` setting on NVIDIA machines, speech-to-text in the fresh setup, and loaded image models
+that are reused. Pins: AbstractGateway 0.7.4, AbstractCore 2.19.2, AbstractRuntime 0.7.3,
+AbstractVoice 0.13.2, AbstractVision 0.3.33 and Abstract3D 0.3.2; the gateway's terminal console is
+`abstractgateway-console` 0.11.2, and the browser client AbstractCode web is 0.6.2. Every other
+version, and the other terminal clients, are unchanged from 0.6.2.
+
+### Added
+
+- **The `gpu` setting on Linux + NVIDIA, rehearsed on real hardware with this release.** On
+  Ubuntu 26.04 with a Quadro RTX 5000 (16 GB, driver 595.91.07, CUDA 13.2; 4 vCPU, 26 GB RAM),
+  `install.sh` installed this release's candidate versions from PyPI in 3 min 1 s (AbstractGateway
+  0.7.3, AbstractCore 2.19.1, AbstractRuntime 0.7.2, AbstractVoice 0.13.1 and AbstractVision 0.3.32;
+  the patch releases listed under Fixed came after this run). The previous
+  install had been removed with `uninstall.sh --yes --purge` and uv's download cache cleared; model
+  weights, LM Studio and a Rust toolchain were already on the machine. The Python packages took 39 s
+  (about 5.8 GB of wheels), llama.cpp's `cu130` build 18 s (726 MB), compiling the two terminal
+  clients with cargo 110 s, and the start and health check 5 s. The install added 14.2 GB on disk.
+  Its checks reported PyTorch 2.11.0 on CUDA 13.0, llama.cpp 0.3.35 (`cu130`) with GPU offload and
+  Whisper on the GPU. Run again, it reported "already up to date" in 10 s. With **Use recommended
+  defaults** and the model weights already downloaded:
+  - text with LM Studio (`qwen/qwen3.5-9b`, Q4_K_M, 6.5 GB on the GPU): the first gateway request
+    took 23 s including loading the model, the next 12 s for a 318-token answer (308 of them
+    reasoning); from AbstractCore in Python about 41 tokens/s;
+  - text-to-speech with Supertonic, on the processor: 1.1 to 1.4 s per sentence (3.2 s for the
+    first gateway request);
+  - image generation with FLUX.2 [klein] 4B through Diffusers, with model CPU offload (7.8 GB
+    peak): 41 s to load the model, then 15 to 16 s per 1024x1024 image. Each gateway image request
+    loads the model again, so one request takes 54 to 59 s;
+  - speech-to-text did not work as installed; see Known issues below.
+
+  vLLM 0.22.1 installs with the gpu setting but was not validated: it needs a C compiler
+  (`build-essential`) the first time it starts a model, and on GPUs older than compute capability
+  8.0 the `--attention-backend TRITON_ATTN` option. See
+  [GPU on Linux (NVIDIA)](docs/install.md#gpu-on-linux-nvidia).
+- **`install.sh` on Linux + NVIDIA** installs llama.cpp's CUDA build that matches PyTorch's CUDA
+  (PyPI's PyTorch for Linux is a CUDA 13 build, which needs NVIDIA driver 580 or newer; with an
+  older driver PyTorch and llama.cpp run on the processor) and keeps it only when it
+  loads and offloads to the GPU; otherwise the CPU build goes back and the summary says why. At the
+  end it checks that PyTorch sees the GPU and which device Whisper uses (`PyTorch:`, `GGUF:` and
+  `Voice:` summary lines), and warns when no C compiler is found for vLLM.
+- **`install.ps1` on Windows + NVIDIA** picks the GPU stack from `nvidia-smi` (CUDA 13 with driver
+  580 or newer and compute capability 7.5 or newer, CUDA 12 with driver 525 or newer, otherwise the
+  CPU), installs PyTorch's CUDA build and llama.cpp's matching prebuilt build (CUDA, then Vulkan,
+  then CPU), and ends with GPU checks that replace any part that does not work with one that does.
+  The Windows gpu setting is implemented and tested with simulated drivers and wheel-only
+  resolves, but it has **not yet been validated on real NVIDIA hardware**. See
+  [GPU on Windows (NVIDIA)](docs/install.md#gpu-on-windows-nvidia).
+- **Live installer progress.** Both installers show uv's output as it comes, with a
+  `still working (… elapsed; last: …)` line after 15 seconds of silence, so a multi-GB download no
+  longer looks frozen. `install.ps1` announces the big downloads before they start.
+
+### Changed
+
+- **Only the three install settings in hints.** Every install hint across the framework names
+  light (`pip install -U abstractcore`), `abstractcore[apple]` or `abstractcore[gpu]`, or says that
+  a capability is not available on this machine, never a bare package or a plugin's own extra
+  (AbstractCore 2.19.1, AbstractGateway 0.7.3, AbstractVoice 0.13.1, AbstractRuntime 0.7.2,
+  Abstract3D 0.3.2).
+- **Smaller gpu setting.** The gpu setting no longer installs MLX-Gen (AbstractVision 0.3.32):
+  about 2.1 GB less on Linux, and it installs on Linux distributions with an older glibc.
+- **`abstractcore[gpu]` installs on Windows with wheels only** (vLLM is Linux only;
+  stable-diffusion.cpp and llama.cpp are left to the installer's prebuilt builds on Windows).
+- **Recommendations on NVIDIA machines.** **Use recommended defaults** picks FLUX.2 [klein] 4B
+  through Diffusers for image generation on an NVIDIA GPU (it fits a 16 GB card), and the LM Studio
+  text download is `qwen/qwen3.5-9b@q4_k_m`, which LM Studio offers on Linux and Windows.
+- **AbstractRuntime depends on AbstractCore's three settings** (`abstractcore`, `[apple]`, `[gpu]`),
+  and `openai` 2.x is allowed across the stack, so the gpu setting resolves a current vLLM.
+
+### Fixed
+
+- **The approval gate shows in every client.** When the agent's tool call waits for approval, a
+  browser or phone that opens the same conversation later now shows the same Allow / Deny card and
+  "Approval needed" as the client that started the turn, instead of "Running a tool" and a Steer box
+  (AbstractCode web 0.6.2 with `@abstractframework/panel-chat` 0.1.20; two-browser end-to-end test).
+- **Speech-to-text without an OpenAI key.** Transcription runs on the configured `input.voice`
+  route (for example local Whisper) and no longer needs TTS credentials (AbstractCore 2.19.1,
+  AbstractVoice 0.13.1).
+- **Speech-to-text in the fresh setup.** The fresh-install defaults and **Use recommended defaults**
+  set speech input (`input.voice`: faster-whisper, model `base`) with text, voice and images, so a
+  new install transcribes locally without an OpenAI key (AbstractCore 2.19.2, AbstractGateway
+  0.7.4). An install that earlier release defaults seeded gains the route once, when it is empty; a
+  route you set yourself is kept. PyAV is held below 19, which faster-whisper 1.2.1 needs to read
+  audio files (AbstractVoice 0.13.2).
+- **Use recommended defaults saves every route it reports**, including on a fresh install right
+  after the console read the routes (AbstractCore 2.19.2).
+- **Whisper on NVIDIA GPUs.** faster-whisper uses CUDA only when CUDA 12 cuBLAS loads (installed
+  with the gpu setting on Linux and Windows), and otherwise runs on the CPU with a warning.
+- **llama.cpp on CUDA** loads without importing PyTorch first on Linux, and a GGUF model too large
+  for the GPU at its full context tries smaller contexts on the GPU before falling back to the CPU.
+- **Image generation on smaller GPUs.** A Diffusers pipeline that does not fit the GPU's free
+  memory loads with model CPU offload instead of failing with CUDA out of memory. When even the
+  largest component does not fit (for example next to a loaded text model), it falls back to
+  sequential CPU offload, which uses much less GPU memory and is slower per step (AbstractVision
+  0.3.33). On the Quadro RTX 5000, FLUX.2 [klein] 4B at 768x768 and 4 steps peaked near 1.4 GB and
+  took 10.9 to 15.6 s, against 13.4 to 18.5 s with model CPU offload; at about 2.3 s per step
+  against 1.5 s, models that run many steps are slower with it.
+- **A loaded image model is reused.** After **Load** in the console (or `POST /models/load`), image
+  and video requests for that model run on the loaded pipeline instead of loading the model again
+  for each request (AbstractRuntime 0.7.3, AbstractGateway 0.7.4). On the rehearsal machine,
+  FLUX.2 [klein] 4B images through the gateway took 17 to 19 s each instead of 54 to 59 s. A model
+  that was not loaded still runs each request in its own process.
+- **Unloading an image model frees its memory.** On CUDA, FLUX.2 [klein] 4B with model CPU offload
+  left 16.3 GB held after an unload; it now leaves 0.86 GB (AbstractVision 0.3.33).
+
+### Security
+
+- **Email connections verify TLS.** AbstractCore's mail tools (`list_emails`, `read_email`,
+  `send_email`) and the gateway's email bridge check the server certificate and host name, and refuse
+  before login when the check fails; a server signed by a private CA is trusted with the new
+  `ca_file` field of an account (AbstractCore 2.19.2, AbstractGateway 0.7.4).
+- **Automations no longer email anyone the model chooses.** With the default automatic tool
+  approval, message-sending tools are no longer pre-approved: a `send_email` to your registered
+  email runs unattended, any other recipient waits for your approval (AbstractRuntime 0.7.3,
+  AbstractGateway 0.7.4).
+- A `password_env_var` / `imap_password_env_var` that is not an environment variable name is refused
+  instead of being read as the password (AbstractCore 2.19.2, AbstractGateway 0.7.4).
+
+### Found in the rehearsal
+
+Found in the rehearsal on the Quadro RTX 5000 described above, which ran the candidate versions. The
+Fixed entries above address each one.
+
+- **Speech-to-text failed on a fresh gpu install**, for two reasons:
+  - **Use recommended defaults** did not set the speech input route (`input.voice`). With no route,
+    transcription used OpenAI and failed with "OpenAI audio requires OPENAI_API_KEY".
+  - PyAV 19.0.0, released on 2026-09-29, removed an option that faster-whisper 1.2.1 uses to read
+    audio files. Every transcription through the gateway then failed with `open() got an unexpected
+    keyword argument 'metadata_errors'`.
+
+  With the route set to faster-whisper `base` by hand and PyAV 18, faster-whisper transcribed on the
+  GPU with no OpenAI key: 1.0 to 2.3 s per gateway request, and 0.3 GB of GPU memory.
+- **An image next to a loaded text model ran out of GPU memory on a 16 GB card.** LM Studio's
+  `qwen/qwen3.5-9b` keeps 6.5 GB on the GPU while it is loaded. FLUX.2 [klein] needed 7.8 GB even
+  with model CPU offload, so the image request failed with CUDA out of memory after three attempts
+  (about 2.5 minutes). With the text model unloaded (`lms unload --all`, or the console's model
+  list), the same request worked. In this case AbstractVision 0.3.33 falls back to sequential CPU
+  offload (see Fixed above).
+- **Use recommended defaults could skip the image route on a fresh install.** On an NVIDIA machine,
+  if the button was used within a few seconds of the console reading the routes, it could report the
+  image route as already set without saving it. Using it again saved it.
+
 ## [0.6.2] - 2026-09-29
 
 One line installs, upgrades and repairs AbstractFramework, and **Update** in the consoles and the

{abstractframework-0.6.2/abstractframework.egg-info → abstractframework-0.7.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstractframework
-Version: 0.6.2
+Version: 0.7.0
 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.7.2
-Requires-Dist: abstractassistant==0.9.1
-Requires-Dist: abstractcore==2.19.0
-Requires-Dist: AbstractRuntime==0.7.1
+Requires-Dist: abstractgateway==0.8.0
+Requires-Dist: abstractassistant==0.10.0
+Requires-Dist: abstractcore==2.20.1
+Requires-Dist: AbstractRuntime==0.8.0
 Requires-Dist: abstractagent==0.3.17
 Requires-Dist: abstractskill==0.3.0
 Requires-Dist: AbstractMemory==0.3.0
 Requires-Dist: abstractsemantics==0.0.5
-Requires-Dist: abstractvoice==0.13.0
-Requires-Dist: abstractvision==0.3.31
+Requires-Dist: abstractvoice==0.13.2
+Requires-Dist: abstractvision==0.3.33
 Requires-Dist: abstractmusic==0.1.15
-Requires-Dist: abstract3d==0.3.1
+Requires-Dist: abstract3d==0.3.2
 Provides-Extra: apple
-Requires-Dist: abstractgateway[apple]==0.7.2; extra == "apple"
-Requires-Dist: abstractassistant[apple]==0.9.1; platform_system == "Darwin" and extra == "apple"
+Requires-Dist: abstractgateway[apple]==0.8.0; extra == "apple"
+Requires-Dist: abstractassistant[apple]==0.10.0; platform_system == "Darwin" and extra == "apple"
 Provides-Extra: gpu
-Requires-Dist: abstractgateway[gpu]==0.7.2; extra == "gpu"
-Requires-Dist: abstractassistant[gpu]==0.9.1; extra == "gpu"
+Requires-Dist: abstractgateway[gpu]==0.8.0; extra == "gpu"
+Requires-Dist: abstractassistant[gpu]==0.10.0; extra == "gpu"
 Dynamic: license-file
 
 # AbstractFramework
@@ -89,6 +89,13 @@ once: it reads your earlier options from what is installed (or repeat them once)
 button of gateway 0.7.1 cannot upgrade. Gateway only, apps, and version checks:
 [Upgrade](docs/install.md#upgrade).
 
+On Linux or Windows with an NVIDIA GPU (`nvidia-smi` works), the installer picks the `gpu` profile:
+PyTorch and llama.cpp on CUDA, Whisper on the GPU, Diffusers image generation. On Linux it needs
+NVIDIA driver 580 or newer. Its release candidate was rehearsed on a Quadro RTX 5000 on Ubuntu
+26.04; the measured results, and what the final versions changed, are in GPU on Linux. The Windows gpu install is
+implemented but not yet validated on real NVIDIA hardware. See [GPU on Linux](docs/install.md#gpu-on-linux-nvidia) and
+[GPU on Windows](docs/install.md#gpu-on-windows-nvidia).
+
 The installer sets up the gateway in your user account (no admin password, no system Python),
 with local voice (Supertonic text-to-speech and Whisper speech-to-text), asks whether to start it
 at login (Enter = yes; an unattended install leaves it off and says how to turn it on), starts it
@@ -161,7 +168,8 @@ Start here if you're building persistent AI applications — agents that run for
 
 - Durable execution that survives crashes and restarts
 - Append-only ledger (replay-first) for auditability
-- Automations: a workflow that runs on a fixed interval or on demand, kept as a readable conversation ([Automations](docs/automations.md))
+- Automations: a workflow that runs on a fixed interval, when an email arrives, or on demand, kept as a readable conversation ([Automations](docs/automations.md))
+- Email for each user: connect your own mailbox, get automation results and approvals by email, and let agents use email tools when an administrator allows it ([Email](https://github.com/lpalbou/AbstractGateway/blob/main/docs/email.md))
 - Multi-client: terminal, browser, tray, Telegram, email
 - Start on one device, continue on another
 
@@ -209,7 +217,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.7.2` and `ghcr.io/lpalbou/abstractcore-server:2.19.0`.
+`ghcr.io/lpalbou/abstractgateway:0.8.0` and `ghcr.io/lpalbou/abstractcore-server:2.20.1`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -353,9 +361,9 @@ pip install "abstractframework[gpu]"
 |---|---|---|---|
 | Light | `pip install abstractframework` | macOS, Linux, Windows | 3.10–3.13 |
 | Apple | `pip install "abstractframework[apple]"` | macOS 14+ on Apple Silicon | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
-| GPU | `pip install "abstractframework[gpu]"` | Linux / Windows with a CUDA or ROCm GPU | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
+| GPU | `pip install "abstractframework[gpu]"` | Linux with a CUDA or ROCm GPU; on Windows, use the one-line installer (a plain pip install gets PyPI's CPU-only PyTorch and no llama.cpp) | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
 
-### Release matrix (abstractframework 0.6.2)
+### Release matrix (abstractframework 0.7.0)
 
 `abstractframework` pins every Python package with `==`, so one version of the
 meta-package always installs the same stack. The browser apps and Rust tools are
@@ -364,32 +372,32 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.7.2 |
-| PyPI | `abstractassistant` | 0.9.1 |
-| PyPI | `abstractcore` | 2.19.0 |
-| PyPI | `AbstractRuntime` | 0.7.1 |
+| PyPI | `abstractgateway` | 0.8.0 |
+| PyPI | `abstractassistant` | 0.10.0 |
+| PyPI | `abstractcore` | 2.20.1 |
+| PyPI | `AbstractRuntime` | 0.8.0 |
 | PyPI | `abstractagent` | 0.3.17 |
 | PyPI | `abstractskill` | 0.3.0 |
 | PyPI | `AbstractMemory` | 0.3.0 |
 | PyPI | `abstractsemantics` | 0.0.5 |
-| PyPI | `abstractvoice` | 0.13.0 |
-| PyPI | `abstractvision` | 0.3.31 |
+| PyPI | `abstractvoice` | 0.13.2 |
+| PyPI | `abstractvision` | 0.3.33 |
 | PyPI | `abstractmusic` | 0.1.15 |
-| PyPI | `abstract3d` | 0.3.1 |
+| PyPI | `abstract3d` | 0.3.2 |
 | npm | `@abstractframework/flow` | 0.4.0 |
-| npm | `@abstractframework/code` | 0.6.1 |
-| npm | `@abstractframework/observer` | 0.2.1 |
+| npm | `@abstractframework/code` | 0.7.0 |
+| npm | `@abstractframework/observer` | 0.3.0 |
 | npm | `@abstractframework/continuum` | 0.4.0 |
 | npm | `@abstractframework/entity` | 0.3.0 |
 | crates.io | `abstractcode` | 0.7.1 |
-| crates.io | `abstractgateway-console` | 0.11.1 |
-| crates.io | `abstractcore-console` | 0.4.1 |
+| crates.io | `abstractgateway-console` | 0.12.0 |
+| crates.io | `abstractcore-console` | 0.5.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.7.2 (`gpu-latest` / `<version>-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.19.0 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.8.0 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.20.1 |
 
 `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.0). `abstractskill` (pinned above)
+not part of any profile installs separately: `pip install abstractcamera` (0.2.1). `abstractskill` (pinned above)
 comes with the gateway, which carries its curated skill shelf; install it on its own with
 `pip install abstractskill`.
 

{abstractframework-0.6.2 → abstractframework-0.7.0}/README.md

@@ -44,6 +44,13 @@ once: it reads your earlier options from what is installed (or repeat them once)
 button of gateway 0.7.1 cannot upgrade. Gateway only, apps, and version checks:
 [Upgrade](docs/install.md#upgrade).
 
+On Linux or Windows with an NVIDIA GPU (`nvidia-smi` works), the installer picks the `gpu` profile:
+PyTorch and llama.cpp on CUDA, Whisper on the GPU, Diffusers image generation. On Linux it needs
+NVIDIA driver 580 or newer. Its release candidate was rehearsed on a Quadro RTX 5000 on Ubuntu
+26.04; the measured results, and what the final versions changed, are in GPU on Linux. The Windows gpu install is
+implemented but not yet validated on real NVIDIA hardware. See [GPU on Linux](docs/install.md#gpu-on-linux-nvidia) and
+[GPU on Windows](docs/install.md#gpu-on-windows-nvidia).
+
 The installer sets up the gateway in your user account (no admin password, no system Python),
 with local voice (Supertonic text-to-speech and Whisper speech-to-text), asks whether to start it
 at login (Enter = yes; an unattended install leaves it off and says how to turn it on), starts it
@@ -116,7 +123,8 @@ Start here if you're building persistent AI applications — agents that run for
 
 - Durable execution that survives crashes and restarts
 - Append-only ledger (replay-first) for auditability
-- Automations: a workflow that runs on a fixed interval or on demand, kept as a readable conversation ([Automations](docs/automations.md))
+- Automations: a workflow that runs on a fixed interval, when an email arrives, or on demand, kept as a readable conversation ([Automations](docs/automations.md))
+- Email for each user: connect your own mailbox, get automation results and approvals by email, and let agents use email tools when an administrator allows it ([Email](https://github.com/lpalbou/AbstractGateway/blob/main/docs/email.md))
 - Multi-client: terminal, browser, tray, Telegram, email
 - Start on one device, continue on another
 
@@ -164,7 +172,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.7.2` and `ghcr.io/lpalbou/abstractcore-server:2.19.0`.
+`ghcr.io/lpalbou/abstractgateway:0.8.0` and `ghcr.io/lpalbou/abstractcore-server:2.20.1`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -308,9 +316,9 @@ pip install "abstractframework[gpu]"
 |---|---|---|---|
 | Light | `pip install abstractframework` | macOS, Linux, Windows | 3.10–3.13 |
 | Apple | `pip install "abstractframework[apple]"` | macOS 14+ on Apple Silicon | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
-| GPU | `pip install "abstractframework[gpu]"` | Linux / Windows with a CUDA or ROCm GPU | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
+| GPU | `pip install "abstractframework[gpu]"` | Linux with a CUDA or ROCm GPU; on Windows, use the one-line installer (a plain pip install gets PyPI's CPU-only PyTorch and no llama.cpp) | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
 
-### Release matrix (abstractframework 0.6.2)
+### Release matrix (abstractframework 0.7.0)
 
 `abstractframework` pins every Python package with `==`, so one version of the
 meta-package always installs the same stack. The browser apps and Rust tools are
@@ -319,32 +327,32 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.7.2 |
-| PyPI | `abstractassistant` | 0.9.1 |
-| PyPI | `abstractcore` | 2.19.0 |
-| PyPI | `AbstractRuntime` | 0.7.1 |
+| PyPI | `abstractgateway` | 0.8.0 |
+| PyPI | `abstractassistant` | 0.10.0 |
+| PyPI | `abstractcore` | 2.20.1 |
+| PyPI | `AbstractRuntime` | 0.8.0 |
 | PyPI | `abstractagent` | 0.3.17 |
 | PyPI | `abstractskill` | 0.3.0 |
 | PyPI | `AbstractMemory` | 0.3.0 |
 | PyPI | `abstractsemantics` | 0.0.5 |
-| PyPI | `abstractvoice` | 0.13.0 |
-| PyPI | `abstractvision` | 0.3.31 |
+| PyPI | `abstractvoice` | 0.13.2 |
+| PyPI | `abstractvision` | 0.3.33 |
 | PyPI | `abstractmusic` | 0.1.15 |
-| PyPI | `abstract3d` | 0.3.1 |
+| PyPI | `abstract3d` | 0.3.2 |
 | npm | `@abstractframework/flow` | 0.4.0 |
-| npm | `@abstractframework/code` | 0.6.1 |
-| npm | `@abstractframework/observer` | 0.2.1 |
+| npm | `@abstractframework/code` | 0.7.0 |
+| npm | `@abstractframework/observer` | 0.3.0 |
 | npm | `@abstractframework/continuum` | 0.4.0 |
 | npm | `@abstractframework/entity` | 0.3.0 |
 | crates.io | `abstractcode` | 0.7.1 |
-| crates.io | `abstractgateway-console` | 0.11.1 |
-| crates.io | `abstractcore-console` | 0.4.1 |
+| crates.io | `abstractgateway-console` | 0.12.0 |
+| crates.io | `abstractcore-console` | 0.5.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.7.2 (`gpu-latest` / `<version>-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.19.0 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.8.0 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.20.1 |
 
 `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.0). `abstractskill` (pinned above)
+not part of any profile installs separately: `pip install abstractcamera` (0.2.1). `abstractskill` (pinned above)
 comes with the gateway, which carries its curated skill shelf; install it on its own with
 `pip install abstractskill`.
 

{abstractframework-0.6.2 → abstractframework-0.7.0}/abstractframework/__init__.py

@@ -10,23 +10,23 @@ Most implementation functionality still lives in component projects.
 
 from __future__ import annotations
 
-__version__ = "0.6.2"
+__version__ = "0.7.0"
 __author__ = "Laurent-Philippe Albou"
 __license__ = "MIT"
 
 RELEASE_VERSIONS: dict[str, str] = {
-    "abstractcore": "2.19.0",
-    "abstractruntime": "0.7.1",
+    "abstractcore": "2.20.1",
+    "abstractruntime": "0.8.0",
     "abstractagent": "0.3.17",
-    "abstractgateway": "0.7.2",
+    "abstractgateway": "0.8.0",
     "abstractskill": "0.3.0",
     "abstractmemory": "0.3.0",
     "abstractsemantics": "0.0.5",
-    "abstractvoice": "0.13.0",
-    "abstractvision": "0.3.31",
+    "abstractvoice": "0.13.2",
+    "abstractvision": "0.3.33",
     "abstractmusic": "0.1.15",
-    "abstract3d": "0.3.1",
-    "abstractassistant": "0.9.1",
+    "abstract3d": "0.3.2",
+    "abstractassistant": "0.10.0",
 }
 
 PACKAGE_DISTRIBUTIONS: dict[str, str] = {
@@ -46,8 +46,8 @@ PACKAGE_DISTRIBUTIONS: dict[str, str] = {
 
 NPM_RELEASE_VERSIONS: dict[str, str] = {
     "@abstractframework/flow": "0.4.0",
-    "@abstractframework/code": "0.6.1",
-    "@abstractframework/observer": "0.2.1",
+    "@abstractframework/code": "0.7.0",
+    "@abstractframework/observer": "0.3.0",
     "@abstractframework/continuum": "0.4.0",
     "@abstractframework/entity": "0.3.0",
 }
@@ -55,8 +55,8 @@ NPM_RELEASE_VERSIONS: dict[str, str] = {
 # Terminal tools published on crates.io alongside this release (installed with `cargo install`,
 # or by the bootstrap scripts: the gateway console and abstractcode by default).
 CRATE_RELEASE_VERSIONS: dict[str, str] = {
-    "abstractgateway-console": "0.11.1",
-    "abstractcore-console": "0.4.1",
+    "abstractgateway-console": "0.12.0",
+    "abstractcore-console": "0.5.0",
     "abstractcode": "0.7.1",
     "abstracttui": "0.6.0",
 }