abstractframework 0.6.3__tar.gz → 0.7.1__tar.gz

{abstractframework-0.6.3 → abstractframework-0.7.1}/CHANGELOG.md

@@ -4,6 +4,132 @@ All notable changes to AbstractFramework will be documented in this file.
 
 ## [Unreleased]
 
+## [0.7.1] - 2026-09-30
+
+A patch release. Pins: AbstractCore 2.20.2, AbstractRuntime 0.8.1 and AbstractGateway 0.8.1; every
+other version (the terminal consoles, the browser apps, AbstractAssistant 0.10.0) is unchanged
+from 0.7.0.
+
+### Fixed
+
+- **Email automations never trigger themselves.** An automation set to "Email me the result" whose
+  filter matched its own result email ran again on every result. Every message the framework sends
+  automatically (notifications, sign-in codes, anything an automation sends) now carries
+  `Auto-Submitted: auto-generated` (RFC 3834) and an `X-AbstractFramework-Automation` header, its
+  Message-ID is recorded, and the mail watcher never runs an automation on your own automatic
+  mail. **When an email arrives** also ignores automatic mail from others (auto-replies, vacation
+  notices) by default; its `auto_submitted: "admit"` option turns that off. See the gateway's
+  email guide.
+- **Voice on a light install.** Text-to-speech returned an error on a fresh light install of a
+  large Mac: the recommended text model there was an MLX build, which the light profile does not
+  install, and speech went through the text model. Speech, transcription and image generation no
+  longer need a text model, and recommendations only name engines your install has: without MLX
+  the Mac's memory tier runs on LM Studio (`qwen/qwen3.5-9b` below 24 GB, `qwen/qwen3.8-27b` from
+  24 GB). A light install seeded by 0.7.0 keeps its stored route and sees it flagged; set the text
+  route in the console (Models, or Settings) to change it.
+- The gateway no longer marks a media request's child run failed ("workflow ... not registered
+  (after 40 consecutive attempts)").
+- A chat's email to your own address runs without asking, and "your own address" is the one **My
+  email** shows (your user email, else the connected mailbox's address).
+- A run started through the API without a tool list gets the email tools when you turned on agent
+  email tools.
+- Moving a model route to another provider drops the old engine's speculation setting (an LM Studio
+  route no longer keeps an MLX route's `native_mtp`).
+- A live reply no longer misses its end when the run finished just as the gateway was reading its
+  stream.
+- `install.sh` on Linux with an NVIDIA GPU: **The same steps by hand** now include llama.cpp's CUDA
+  build (the listed install line takes its CPU build).
+
+### Changed
+
+- The installers do not build the AbstractCore terminal console (`abstractcore-console`); it is
+  listed with each release and installed with `cargo install abstractcore-console` for a
+  standalone `abstractcore serve` (the gateway's terminal console has its Models and Engines
+  screens). See [Install](docs/install.md#apps-and-tools-outside-pip).
+
+## [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

{abstractframework-0.6.3/abstractframework.egg-info → abstractframework-0.7.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstractframework
-Version: 0.6.3
+Version: 0.7.1
 Summary: Unified installer and documentation hub for the AbstractFramework ecosystem
 Author-email: Laurent-Philippe Albou <contact@abstractframework.ai>
 License: MIT
@@ -23,10 +23,10 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: abstractgateway==0.7.4
-Requires-Dist: abstractassistant==0.9.1
-Requires-Dist: abstractcore==2.19.2
-Requires-Dist: AbstractRuntime==0.7.3
+Requires-Dist: abstractgateway==0.8.1
+Requires-Dist: abstractassistant==0.10.0
+Requires-Dist: abstractcore==2.20.2
+Requires-Dist: AbstractRuntime==0.8.1
 Requires-Dist: abstractagent==0.3.17
 Requires-Dist: abstractskill==0.3.0
 Requires-Dist: AbstractMemory==0.3.0
@@ -36,11 +36,11 @@ Requires-Dist: abstractvision==0.3.33
 Requires-Dist: abstractmusic==0.1.15
 Requires-Dist: abstract3d==0.3.2
 Provides-Extra: apple
-Requires-Dist: abstractgateway[apple]==0.7.4; extra == "apple"
-Requires-Dist: abstractassistant[apple]==0.9.1; platform_system == "Darwin" and extra == "apple"
+Requires-Dist: abstractgateway[apple]==0.8.1; extra == "apple"
+Requires-Dist: abstractassistant[apple]==0.10.0; platform_system == "Darwin" and extra == "apple"
 Provides-Extra: gpu
-Requires-Dist: abstractgateway[gpu]==0.7.4; extra == "gpu"
-Requires-Dist: abstractassistant[gpu]==0.9.1; extra == "gpu"
+Requires-Dist: abstractgateway[gpu]==0.8.1; extra == "gpu"
+Requires-Dist: abstractassistant[gpu]==0.10.0; extra == "gpu"
 Dynamic: license-file
 
 # AbstractFramework
@@ -168,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
 
@@ -216,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.4` and `ghcr.io/lpalbou/abstractcore-server:2.19.2`.
+`ghcr.io/lpalbou/abstractgateway:0.8.1` and `ghcr.io/lpalbou/abstractcore-server:2.20.2`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -362,7 +363,7 @@ pip install "abstractframework[gpu]"
 | 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 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.3)
+### Release matrix (abstractframework 0.7.1)
 
 `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
@@ -371,10 +372,10 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.7.4 |
-| PyPI | `abstractassistant` | 0.9.1 |
-| PyPI | `abstractcore` | 2.19.2 |
-| PyPI | `AbstractRuntime` | 0.7.3 |
+| PyPI | `abstractgateway` | 0.8.1 |
+| PyPI | `abstractassistant` | 0.10.0 |
+| PyPI | `abstractcore` | 2.20.2 |
+| PyPI | `AbstractRuntime` | 0.8.1 |
 | PyPI | `abstractagent` | 0.3.17 |
 | PyPI | `abstractskill` | 0.3.0 |
 | PyPI | `AbstractMemory` | 0.3.0 |
@@ -384,16 +385,16 @@ and tested together.
 | PyPI | `abstractmusic` | 0.1.15 |
 | PyPI | `abstract3d` | 0.3.2 |
 | npm | `@abstractframework/flow` | 0.4.0 |
-| npm | `@abstractframework/code` | 0.6.2 |
-| 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.2 |
-| 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.4 (`gpu-latest` / `<version>-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.19.2 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.8.1 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.20.2 |
 
 `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.6.3 → abstractframework-0.7.1}/README.md

@@ -123,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
 
@@ -171,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.4` and `ghcr.io/lpalbou/abstractcore-server:2.19.2`.
+`ghcr.io/lpalbou/abstractgateway:0.8.1` and `ghcr.io/lpalbou/abstractcore-server:2.20.2`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -317,7 +318,7 @@ pip install "abstractframework[gpu]"
 | 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 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.3)
+### Release matrix (abstractframework 0.7.1)
 
 `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
@@ -326,10 +327,10 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.7.4 |
-| PyPI | `abstractassistant` | 0.9.1 |
-| PyPI | `abstractcore` | 2.19.2 |
-| PyPI | `AbstractRuntime` | 0.7.3 |
+| PyPI | `abstractgateway` | 0.8.1 |
+| PyPI | `abstractassistant` | 0.10.0 |
+| PyPI | `abstractcore` | 2.20.2 |
+| PyPI | `AbstractRuntime` | 0.8.1 |
 | PyPI | `abstractagent` | 0.3.17 |
 | PyPI | `abstractskill` | 0.3.0 |
 | PyPI | `AbstractMemory` | 0.3.0 |
@@ -339,16 +340,16 @@ and tested together.
 | PyPI | `abstractmusic` | 0.1.15 |
 | PyPI | `abstract3d` | 0.3.2 |
 | npm | `@abstractframework/flow` | 0.4.0 |
-| npm | `@abstractframework/code` | 0.6.2 |
-| 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.2 |
-| 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.4 (`gpu-latest` / `<version>-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.19.2 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.8.1 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.20.2 |
 
 `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.6.3 → abstractframework-0.7.1}/abstractframework/__init__.py

@@ -10,15 +10,15 @@ Most implementation functionality still lives in component projects.
 
 from __future__ import annotations
 
-__version__ = "0.6.3"
+__version__ = "0.7.1"
 __author__ = "Laurent-Philippe Albou"
 __license__ = "MIT"
 
 RELEASE_VERSIONS: dict[str, str] = {
-    "abstractcore": "2.19.2",
-    "abstractruntime": "0.7.3",
+    "abstractcore": "2.20.2",
+    "abstractruntime": "0.8.1",
     "abstractagent": "0.3.17",
-    "abstractgateway": "0.7.4",
+    "abstractgateway": "0.8.1",
     "abstractskill": "0.3.0",
     "abstractmemory": "0.3.0",
     "abstractsemantics": "0.0.5",
@@ -26,7 +26,7 @@ RELEASE_VERSIONS: dict[str, str] = {
     "abstractvision": "0.3.33",
     "abstractmusic": "0.1.15",
     "abstract3d": "0.3.2",
-    "abstractassistant": "0.9.1",
+    "abstractassistant": "0.10.0",
 }
 
 PACKAGE_DISTRIBUTIONS: dict[str, str] = {
@@ -46,17 +46,20 @@ PACKAGE_DISTRIBUTIONS: dict[str, str] = {
 
 NPM_RELEASE_VERSIONS: dict[str, str] = {
     "@abstractframework/flow": "0.4.0",
-    "@abstractframework/code": "0.6.2",
-    "@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",
 }
 
 # 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).
+# or by the bootstrap scripts: the gateway console and abstractcode by default). The installers
+# never build `abstractcore-console` (0.7.1 decision): it is the console of a standalone
+# `abstractcore serve`, and the gateway's terminal console already carries its Models and
+# Engines screens; it is listed here as a release version only.
 CRATE_RELEASE_VERSIONS: dict[str, str] = {
-    "abstractgateway-console": "0.11.2",
-    "abstractcore-console": "0.4.1",
+    "abstractgateway-console": "0.12.0",
+    "abstractcore-console": "0.5.0",
     "abstractcode": "0.7.1",
     "abstracttui": "0.6.0",
 }

{abstractframework-0.6.3 → abstractframework-0.7.1/abstractframework.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstractframework
-Version: 0.6.3
+Version: 0.7.1
 Summary: Unified installer and documentation hub for the AbstractFramework ecosystem
 Author-email: Laurent-Philippe Albou <contact@abstractframework.ai>
 License: MIT
@@ -23,10 +23,10 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: abstractgateway==0.7.4
-Requires-Dist: abstractassistant==0.9.1
-Requires-Dist: abstractcore==2.19.2
-Requires-Dist: AbstractRuntime==0.7.3
+Requires-Dist: abstractgateway==0.8.1
+Requires-Dist: abstractassistant==0.10.0
+Requires-Dist: abstractcore==2.20.2
+Requires-Dist: AbstractRuntime==0.8.1
 Requires-Dist: abstractagent==0.3.17
 Requires-Dist: abstractskill==0.3.0
 Requires-Dist: AbstractMemory==0.3.0
@@ -36,11 +36,11 @@ Requires-Dist: abstractvision==0.3.33
 Requires-Dist: abstractmusic==0.1.15
 Requires-Dist: abstract3d==0.3.2
 Provides-Extra: apple
-Requires-Dist: abstractgateway[apple]==0.7.4; extra == "apple"
-Requires-Dist: abstractassistant[apple]==0.9.1; platform_system == "Darwin" and extra == "apple"
+Requires-Dist: abstractgateway[apple]==0.8.1; extra == "apple"
+Requires-Dist: abstractassistant[apple]==0.10.0; platform_system == "Darwin" and extra == "apple"
 Provides-Extra: gpu
-Requires-Dist: abstractgateway[gpu]==0.7.4; extra == "gpu"
-Requires-Dist: abstractassistant[gpu]==0.9.1; extra == "gpu"
+Requires-Dist: abstractgateway[gpu]==0.8.1; extra == "gpu"
+Requires-Dist: abstractassistant[gpu]==0.10.0; extra == "gpu"
 Dynamic: license-file
 
 # AbstractFramework
@@ -168,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
 
@@ -216,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.4` and `ghcr.io/lpalbou/abstractcore-server:2.19.2`.
+`ghcr.io/lpalbou/abstractgateway:0.8.1` and `ghcr.io/lpalbou/abstractcore-server:2.20.2`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -362,7 +363,7 @@ pip install "abstractframework[gpu]"
 | 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 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.3)
+### Release matrix (abstractframework 0.7.1)
 
 `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
@@ -371,10 +372,10 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.7.4 |
-| PyPI | `abstractassistant` | 0.9.1 |
-| PyPI | `abstractcore` | 2.19.2 |
-| PyPI | `AbstractRuntime` | 0.7.3 |
+| PyPI | `abstractgateway` | 0.8.1 |
+| PyPI | `abstractassistant` | 0.10.0 |
+| PyPI | `abstractcore` | 2.20.2 |
+| PyPI | `AbstractRuntime` | 0.8.1 |
 | PyPI | `abstractagent` | 0.3.17 |
 | PyPI | `abstractskill` | 0.3.0 |
 | PyPI | `AbstractMemory` | 0.3.0 |
@@ -384,16 +385,16 @@ and tested together.
 | PyPI | `abstractmusic` | 0.1.15 |
 | PyPI | `abstract3d` | 0.3.2 |
 | npm | `@abstractframework/flow` | 0.4.0 |
-| npm | `@abstractframework/code` | 0.6.2 |
-| 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.2 |
-| 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.4 (`gpu-latest` / `<version>-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.19.2 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.8.1 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.20.2 |
 
 `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.6.3 → abstractframework-0.7.1}/abstractframework.egg-info/SOURCES.txt

@@ -188,5 +188,7 @@ scripts/tests/test_inventory.sh
 scripts/tests/test_repo_scripts.sh
 tests/test_install_profiles.py
 tests/test_install_ps1_gpu_stack.py
+tests/test_install_ps1_own_gateway.py
 tests/test_install_sh_gpu_stack.py
+tests/test_install_sh_gpu_twin.py
 tests/test_llms_full.py

{abstractframework-0.6.3 → abstractframework-0.7.1}/abstractframework.egg-info/requires.txt

@@ -1,7 +1,7 @@
-abstractgateway==0.7.4
-abstractassistant==0.9.1
-abstractcore==2.19.2
-AbstractRuntime==0.7.3
+abstractgateway==0.8.1
+abstractassistant==0.10.0
+abstractcore==2.20.2
+AbstractRuntime==0.8.1
 abstractagent==0.3.17
 abstractskill==0.3.0
 AbstractMemory==0.3.0
@@ -12,11 +12,11 @@ abstractmusic==0.1.15
 abstract3d==0.3.2
 
 [apple]
-abstractgateway[apple]==0.7.4
+abstractgateway[apple]==0.8.1
 
 [apple:platform_system == "Darwin"]
-abstractassistant[apple]==0.9.1
+abstractassistant[apple]==0.10.0
 
 [gpu]
-abstractgateway[gpu]==0.7.4
-abstractassistant[gpu]==0.9.1
+abstractgateway[gpu]==0.8.1
+abstractassistant[gpu]==0.10.0

{abstractframework-0.6.3 → abstractframework-0.7.1}/docs/README.md

@@ -37,7 +37,7 @@ Start with **AbstractGateway** + **AbstractFlow**:
 
 - Durable execution that survives crashes and restarts
 - Append-only ledger (replay-first) for auditability
-- Automations: workflows that run on a fixed interval or on demand ([Automations](automations.md))
+- Automations: workflows that run on a fixed interval, when an email arrives, or on demand ([Automations](automations.md))
 - Multi-client: terminal, browser, tray, Telegram, email
 - Start on one device, continue on another
 
@@ -76,9 +76,9 @@ The full component diagram, with memory, semantics and the consoles, is in
 | **[Install](install.md)** | Mac installer, one-line install (`install.sh` / `install.ps1`), start at login, headless or remote install, the local gateway pointer, options, Network setting and uninstall; Light / Apple / GPU chooser, `abstractframework doctor`, installer manifest contract |
 | **[Getting Started](getting-started.md)** | The two entry points + first end-to-end run |
 | **[Agent sessions](agent-sessions.md)** | What every client shares when it chats with an agent: the gateway's default agent workflow, the conversation workspace and its built-in protection, skills, live replies, opening the Assistant signed in |
-| **[Automations](automations.md)** | How automations work in practice and how to manage them: an automation is a durable run, each tick a turn; independent vs growing context; creating one from the Assistant, the Observer or a workflow's defaults; two worked examples; reading results in every client; pause, run now, resume, edit, archive, discuss; notifications, typed waits, restart safety, limits, troubleshooting |
+| **[Automations](automations.md)** | How automations work in practice and how to manage them: an automation is a durable run, each tick a turn; independent vs growing context; creating one from the Assistant, the Observer, AbstractCode or a workflow's defaults; email triggers and email notifications; two worked examples; reading results in every client; pause, run now, resume, edit, archive, discuss; notifications, typed waits, restart safety, limits, troubleshooting |
 | **[Architecture](architecture.md)** | Component diagram, distribution by registry, how a turn flows and the live-reply lane, app proxies, model eject, framework identity, durable execution primitives, comparisons |
-| **[Configuration](configuration.md)** | Minimal config, where defaults live, Core vs Gateway |
+| **[Configuration](configuration.md)** | Minimal config, where defaults live, Core vs Gateway, email accounts |
 | **[Workspace scripts](workspace-scripts.md)** | Working from source: package inventory and tiers, `build.sh`, `status.sh`, `pull.sh`, `commit.sh`, `push.sh`, launchers |
 | **[Glossary](glossary.md)** | Shared terminology (run, ledger, effect, wait, bundle, …) |
 | **[ADR index](adr/README.md)** | Cross-package architectural decisions and accepted platform contracts |

{abstractframework-0.6.3 → abstractframework-0.7.1}/docs/api.md

@@ -55,14 +55,14 @@ The response type returned by `llm.generate(...)`.
 
 ### `__version__`
 
-The meta-package version (`0.6.3` for this release).
+The meta-package version (`0.7.1` for this release).
 
 ### `RELEASE_VERSIONS`
 
-Dictionary mapping each ecosystem package name to the pinned version for this release. In 0.6.3:
-`abstractcore` 2.19.2, `abstractruntime` 0.7.3, `abstractagent` 0.3.17, `abstractgateway` 0.7.4,
+Dictionary mapping each ecosystem package name to the pinned version for this release. In 0.7.1:
+`abstractcore` 2.20.2, `abstractruntime` 0.8.1, `abstractagent` 0.3.17, `abstractgateway` 0.8.1,
 `abstractskill` 0.3.0, `abstractmemory` 0.3.0, `abstractsemantics` 0.0.5, `abstractvoice` 0.13.2, `abstractvision` 0.3.33,
-`abstractmusic` 0.1.15, `abstract3d` 0.3.2, `abstractassistant` 0.9.1.
+`abstractmusic` 0.1.15, `abstract3d` 0.3.2, `abstractassistant` 0.10.0.
 
 ### `PACKAGE_DISTRIBUTIONS`
 
@@ -72,14 +72,14 @@ Maps each package name in `RELEASE_VERSIONS` to its PyPI distribution name (for
 ### `NPM_RELEASE_VERSIONS`
 
 The npm apps released with this version, each runnable with `npx <package>`:
-`@abstractframework/flow` 0.4.0, `@abstractframework/code` 0.6.1,
-`@abstractframework/observer` 0.2.1, `@abstractframework/continuum` 0.4.0 and
+`@abstractframework/flow` 0.4.0, `@abstractframework/code` 0.7.0,
+`@abstractframework/observer` 0.3.0, `@abstractframework/continuum` 0.4.0 and
 `@abstractframework/entity` 0.3.0. They also appear as `npm_apps` in the install manifest.
 
 ### `CRATE_RELEASE_VERSIONS`
 
 The Rust terminal tools released with this version, installed with `cargo install <crate>`:
-`abstractgateway-console` 0.11.2, `abstractcore-console` 0.4.1, `abstractcode` 0.7.1 and the
+`abstractgateway-console` 0.12.0, `abstractcore-console` 0.5.0, `abstractcode` 0.7.1 and the
 `abstracttui` engine 0.6.0. The bootstrap scripts build `abstractgateway-console` at this version by default
 (`--no-console` skips it) and `abstractcode` next to it (`--no-code-cli` skips it).