abstractframework 0.7.1__tar.gz → 0.8.0__tar.gz

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

@@ -4,6 +4,170 @@ All notable changes to AbstractFramework will be documented in this file.
 
 ## [Unreleased]
 
+## [0.8.0] - 2026-10-01
+
+The consoles' email and accounts screens are redesigned, the installer never installs less because
+of the network, and the console and the apps work over https through `tailscale serve`. Pins:
+AbstractGateway 0.10.0, AbstractCore 2.22.0, AbstractRuntime 0.8.2 and AbstractAssistant 0.11.0;
+the terminal consoles `abstractgateway-console` 0.13.0 and `abstractcore-console` 0.6.0 and
+AbstractCode's terminal client `abstractcode` 0.8.0; the
+browser apps Code 0.9.0, Flow 0.6.0, Observer 0.5.0, Continuum 0.6.0 and Entity 0.5.0. Every other
+version is unchanged from 0.7.2.
+
+### Changed
+
+- **Email address and mailbox, named apart.** Your **email address** is where sign-in codes and
+  notifications go; your **mailbox** is the connection your agents and automations read and send
+  with. The mailbox tabs are **IMAP** (first and selected), **Google** and **Microsoft**. The IMAP
+  form shows every server field, pre-filled from the address with the standard settings and then
+  the discovered ones (never over a field you edited), asks for no user name, and offers a Login
+  field only through **My provider uses a different login name**. Connecting fills your email
+  address when it is empty. A connected mailbox has an **Active** switch; **Advanced** holds three
+  sentences: who your agents may send to, "At most 100 per hour and 1000 per day.", and the watch
+  folder. Same layout in the gateway's web and terminal consoles and AbstractCore's.
+- **Send limits default to 100 per hour and 1000 per day** (were 20 and 100). Limits you set
+  yourself are kept on upgrade; an account that kept the old defaults follows the new ones.
+- **Notifications are two switches, Job failed and Approval needed**, both on once a mailbox is
+  connected. **Send a test** answers with a sentence: "Sent to …" or why not ("Not sent: hourly
+  limit reached (100 of 100 this hour) — resets at 14:05."), with reset times in your local time.
+- **One Accounts page.** The gateway web console's **Accounts** page is one table of users and
+  entities (Name with an Admin / User / Entity chip, Email address, Mailbox, Runtime, an **Active** switch; actions Email, Logs,
+  Workspace, Rotate, Manage, Delete, each with its reason when it cannot apply), with **Create
+  user** and **Create entity**. **Email for everyone** below it holds the administrator's
+  **Mailboxes for users** switch, with **Agent email tools for users** and **Sign-in by email**
+  under Advanced. **Logs** shows an account's activity from the gateway's audit log. An
+  administrator sees every account; a user sees only themself and the entities they created, in
+  the consoles and the API.
+- **Sidebar groups and Setup.** The web console groups its pages as Accounts; Work
+  (Workflows, Runtimes, Apps); Models (Providers, Models, Engines, Multimodal); System (Resources,
+  Sandbox, Network). **Setup** at the bottom of the sidebar runs the first-run guide again and keeps
+  your choices unless you replace them. The terminal console uses the same groups and `S` for
+  Setup.
+- **Sign-in by email says what happened.** **Forgot your token? Email me a sign-in code** answers
+  with the outcome: the code is on its way to a masked address, the account has no email address or
+  no mailbox to send from, or the send failed.
+- Every on/off setting in the consoles and the apps is a switch named by what it controls.
+
+### Added
+
+- **https through Tailscale.** `tailscale serve --bg http://127.0.0.1:<port>` on the gateway's
+  computer serves the console and every app at `https://<host>.<tailnet>.ts.net/`, with sign-in,
+  `Secure` cookies and app handover, and the Network setting can stay `localhost`. Voice and camera
+  in the browser need this https address. See
+  [Phones and tablets: Reached through Tailscale](docs/guide/deployment-iphone.md#reached-through-tailscale-https).
+- **The apps work over plain http from another machine.** Opened at `http://<address>:8080/apps/<app>/`
+  (a LAN or Tailscale address), the apps start and copy buttons work; a feature that needs https
+  says so.
+- AbstractCode's web sidebar shows 25 conversations with **Load more**; the Observer opens a run
+  from a `#run/<run_id>` link (the Accounts page's Logs link to it).
+
+### Fixed
+
+- **Transcription no longer shows "Engine missing: unknown AbstractVoice engine 'huggingface'".**
+  The recommended setup stores the transcription engine's route; a route written that way before
+  is repaired when the configuration loads (a backup is written first).
+- **Sign-in through a proxy on the gateway's computer** (such as `tailscale serve`) no longer answers
+  403 "origin not allowed"; app manifests and icons load without an app session.
+- **Pausing an automation also stops its retries**: an occurrence waiting in retry backoff is
+  cancelled.
+- **Resuming an email automation wakes the mail watcher at once**, so mail that arrives right after
+  the resume triggers it.
+- **Two Node.js installs at once** (two apps, or an app and **Install Node.js**) no longer fail one
+  of them; Node.js is downloaded once.
+- **Stopping the gateway while it starts** waits for the startup and stops what it started.
+- **AbstractCore keeps settings it does not know.** A settings save keeps keys you added to
+  `abstractcore.json` and keys written by a newer version.
+- **Server file routes never serve the gateway's data folder or credential folders**, so received
+  mail and run ledgers of other users cannot be read through `/files/read`. Administrators never
+  read mail.
+
+- **An upgrade never installs less because of the network.** A server error while downloading (a
+  502 on PyTorch's wheel) made the installer drop local voice and finish green without it. Now any
+  network failure of a uv install (HTTP 5xx, 429, 408, a DNS, connect, reset or closed connection, a
+  timeout, a download cut off, uv's `Request failed after N retries`) runs the same full install
+  again on the index-lag waits (15, 30, 60, then 120 s; 8 attempts over about 10 minutes), then stops
+  with exit code 1, uv's cause in red and the exact command to run again. uv changes the gateway's
+  environment only after every download succeeded, so the previous gateway stays installed and
+  working. Python's download and nodejs-wheel get
+  the same retries. `install.sh` and `install.ps1`.
+- **Local voice left out is said in red.** The voice fallback now runs only for a deterministic
+  incompatibility (uv's resolution failure, e.g. `has no wheels with a matching platform tag`, a failed
+  build, a broken file). The warning gives uv's reason, the summary's first line says `… but NOT
+  everything was installed:`, the `Voice:` line is red, the output ends with `NOT installed:` and
+  `bootstrap.env` records `VOICE_SKIPPED=<reason>`.
+- **The terminal console and abstractcode wait for crates.io.** Right after a crate publish, `cargo
+  install --version <pin>` answered `could not find ... in registry` and the console was skipped with a
+  warning. crates.io's index lag and cargo's network failures now get the same waits; when they run
+  out the rest of the install goes on, the summary says in red which crate was not built, and the
+  installer exits with code 1.
+- **A port changed in a console survives an upgrade.** A re-run without `--port` (the consoles'
+  **Update**) read the port from `bootstrap.env`, wrote it over the gateway's Network setting and
+  restarted the gateway on the old port. The installer now reads `abstractgateway network status
+  --json` first: a stored port wins, is recorded in `bootstrap.env`, and is never overwritten unless
+  `--port` is given; a stored port held by another program stops the install with what to do
+  instead of moving to another port.
+- **Upgrading an install older than 0.6.1 no longer turns options off.** An option the installer did
+  not have when that install was made (the terminal console before gateway 0.6.0, abstractcode and the
+  AbstractCore commands before gateway 0.7.1) was read as opted out, so a 0.4.0 install kept
+  `--no-core-cli` on its first upgrade. Such an option now takes today's default, dated by the
+  recorded `GATEWAY_VERSION`, and the installer says so.
+
+### Documentation
+
+- The root docs describe the email address and mailbox screens, the Accounts page, the sidebar
+  groups and Setup, sign-in by email, the installer's retry, and https through Tailscale
+  ([Email integration](docs/guide/email-integration.md),
+  [Phones and tablets](docs/guide/deployment-iphone.md), [Install](docs/install.md),
+  [Glossary](docs/glossary.md)).
+- Per-user email in
+  [Email integration](docs/guide/email-integration.md) and the
+  [Email inbox agent](docs/scenarios/email-inbox-agent.md) scenario (settings in the consoles;
+  agent email tools off by default; recipient allowlist starting with your own address; the
+  framework's own automatic mail never triggers an automation; sign-in by email), phones and
+  tablets through the gateway's one address in [Phones and tablets](docs/guide/deployment-iphone.md)
+  and the [Phone thin client](docs/scenarios/phone-thin-client.md) scenario, responsive apps in the
+  README, index, architecture, FAQ and getting started, email terms in the glossary, and email rows
+  in Troubleshooting and Automations.
+
+## [0.7.2] - 2026-09-30
+
+Every screen works on phones, tablets and any window size. Pins: AbstractGateway 0.9.0 and
+AbstractCore 2.21.0 (responsive web consoles); the browser apps Flow 0.5.0, Code 0.8.0, Observer
+0.4.0, Continuum 0.5.0 and Entity 0.4.0 (responsive layouts, on `@abstractframework/ui-kit` 0.3.2
+and `panel-chat` 0.2.1). Every other version is unchanged from 0.7.1.
+
+### Changed
+
+- **Responsive everywhere.** The gateway and AbstractCore web consoles and the five browser apps
+  follow one responsive system: the framework breakpoints (480, 768, 1024 and 1440 px wide, plus
+  500 px tall for phone landscape), sidebars that become drawers below 1024 px, dialogs that open
+  as bottom sheets on small screens, 44 px touch targets and 16 px form fields on touch screens, and
+  pages that respect the notch and home-indicator areas. See each app's changelog for details.
+
+### Fixed
+
+- **A new email automation reacts to the mail you send to test it.** Creating a "When an email
+  arrives" automation wakes the mail watcher, which marks where new mail starts within seconds, so
+  a message sent right after creation is processed.
+- **A new or resumed email automation no longer runs on old mail.** After a time with no email
+  automation active, the next one received everything that had arrived meanwhile as new mail. That
+  mail is now treated as already there (mail that arrives while the gateway itself is down is
+  still read when it is back).
+- **An upgrade right after a release no longer installs less.** When one of PyPI's mirrors had not
+  yet listed a version the release pins, uv answered `there is no version of
+  abstractgateway[gpu]==0.8.1`, and the installer took that for a system without the voice wheels
+  and installed without local voice. install.sh and install.ps1 (and so the consoles' **Update** action, which runs install.sh) now recognise that
+  case from uv's exit code 1, its resolution failure, and its exact-pin wording for a package the
+  installer itself pinned (or from a download of that pinned version's own file that answers 404:
+  the list shows it, the file is not served yet), and run the same install again, with every feature, after 15 s, 30 s,
+  60 s and 120 s waits (8 attempts, about 10 minutes), printing `PyPI hasn't published
+  abstractgateway 0.8.1 to every mirror yet; retrying in 30 s (attempt 3/8)`. After that they stop
+  with the cause and what to do, never with a smaller install. The fallbacks for systems without
+  the voice or llama.cpp wheels are unchanged. The voice requirement now carries the release's
+  AbstractVoice version (`abstractvoice[supertonic,stt]==0.13.2`), which the release matrix already
+  enforced, so uv names a missing AbstractVoice in the same exact-pin form. See
+  [Right after a release](docs/install.md#right-after-a-release).
+
 ## [0.7.1] - 2026-09-30
 
 A patch release. Pins: AbstractCore 2.20.2, AbstractRuntime 0.8.1 and AbstractGateway 0.8.1; every

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstractframework
-Version: 0.7.1
+Version: 0.8.0
 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.8.1
-Requires-Dist: abstractassistant==0.10.0
-Requires-Dist: abstractcore==2.20.2
-Requires-Dist: AbstractRuntime==0.8.1
+Requires-Dist: abstractgateway==0.10.0
+Requires-Dist: abstractassistant==0.11.0
+Requires-Dist: abstractcore==2.22.0
+Requires-Dist: AbstractRuntime==0.8.2
 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.8.1; extra == "apple"
-Requires-Dist: abstractassistant[apple]==0.10.0; platform_system == "Darwin" and extra == "apple"
+Requires-Dist: abstractgateway[apple]==0.10.0; extra == "apple"
+Requires-Dist: abstractassistant[apple]==0.11.0; platform_system == "Darwin" and extra == "apple"
 Provides-Extra: gpu
-Requires-Dist: abstractgateway[gpu]==0.8.1; extra == "gpu"
-Requires-Dist: abstractassistant[gpu]==0.10.0; extra == "gpu"
+Requires-Dist: abstractgateway[gpu]==0.10.0; extra == "gpu"
+Requires-Dist: abstractassistant[gpu]==0.11.0; extra == "gpu"
 Dynamic: license-file
 
 # AbstractFramework
@@ -91,9 +91,9 @@ button of gateway 0.7.1 cannot upgrade. Gateway only, apps, and version checks:
 
 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
+NVIDIA driver 580 or newer; measured install and per-capability timings on a Quadro RTX 5000 with
+Ubuntu 26.04 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),
@@ -102,7 +102,8 @@ at login (Enter = yes; an unattended install leaves it off and says how to turn
 on `127.0.0.1:8080`, and opens its web console in your browser already signed in. A first-run guide
 then sets up a local engine (Ollama, LM Studio, MLX, llama.cpp), downloads a model that fits your
 machine, and lists the apps; the gateway serves them on its own address at `/apps/<app>/`. The
-installer also builds the terminal console, `abstractgateway-console`, which runs the same guide on
+**Setup** button at the bottom of the console's sidebar runs the guide again, keeping your choices
+unless you replace them. The installer also builds the terminal console, `abstractgateway-console`, which runs the same guide on
 a server without a browser and offers itself at the end of an install over SSH
 ([Headless or remote machine](docs/install.md#headless-or-remote-machine)).
 
@@ -169,9 +170,10 @@ 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, 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))
+- Email for each user: your email address receives sign-in codes and notifications; connect your own mailbox (IMAP, Google or Microsoft) to get failed jobs, approvals and automation results by email, and let your agents use email tools when you switch them on ([Email integration](docs/guide/email-integration.md))
 - Multi-client: terminal, browser, tray, Telegram, email
-- Start on one device, continue on another
+- Start on one device, continue on another: the web console and every browser app work on phones,
+  tablets and any window size ([Phones and tablets](docs/guide/deployment-iphone.md))
 
 ```bash
 pip install abstractgateway
@@ -217,7 +219,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.8.1` and `ghcr.io/lpalbou/abstractcore-server:2.20.2`.
+`ghcr.io/lpalbou/abstractgateway:0.10.0` and `ghcr.io/lpalbou/abstractcore-server:2.22.0`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -311,6 +313,10 @@ The ecosystem, grouped by layer. Each name links to the package's repository.
 
 ### Apps and clients
 
+The gateway's web console and the five browser apps (Code Web UI, Flow Editor, Observer, Entity,
+Continuum) adapt to phones, tablets and windows of any size: drawers below 1024 px, bottom-sheet
+dialogs and touch-sized controls on phones.
+
 | App | What it does | Install |
 |---|---|---|
 | [AbstractCode](https://github.com/lpalbou/AbstractCode) | Terminal agentic dev client (Rust, on the AbstractTUI engine) — durable sessions, tool approvals, the gateway's default workflow, workspace files, live replies | `cargo install abstractcode`, or a prebuilt binary from the [GitHub release](https://github.com/lpalbou/AbstractCode/releases) |
@@ -318,7 +324,7 @@ The ecosystem, grouped by layer. Each name links to the package's repository.
 | [AbstractObserver](https://github.com/lpalbou/AbstractObserver) | Browser UI — monitor, control, and schedule gateway runs | the gateway console's **Apps** page (served at `/apps/observer/`), or `npx @abstractframework/observer --gateway-url <url>` |
 | [AbstractEntity](https://github.com/lpalbou/AbstractEntity) | Summoned-entity manager — roster, blueprint (cognition map + editing), chat drawer, live replay | the gateway console's **Apps** page (served at `/apps/entity/`), or `npx @abstractframework/entity --gateway-url <url>` |
 | [AbstractContinuum](https://github.com/lpalbou/AbstractContinuum) | Continuous iterative development and deployment console | the gateway console's **Apps** page (served at `/apps/continuum/`), or `npx @abstractframework/continuum --gateway-url <url>` |
-| **Gateway consoles** | Operator consoles for a running gateway: web at `/console` (first-run guide, Models, Engines, providers, users), terminal via `abstractgateway-console` (the same setup guide and screens, Network and Apps included, for headless hosts) | built into `abstractgateway`; built by the installer, or `cargo install abstractgateway-console` |
+| **Gateway consoles** | Operator consoles for a running gateway: web at `/console` (sidebar groups Accounts, Work, Models and System; the **Setup** button; one Accounts table of users and entities), terminal via `abstractgateway-console` (the same setup guide and screens, Network and Apps included, for headless hosts) | built into `abstractgateway`; built by the installer, or `cargo install abstractgateway-console` |
 | **Core consoles** | Consoles for AbstractCore: web at `/console` of `abstractcore serve`, terminal via `abstractcore-console` (config, Models, Engines) | built into `abstractcore`; `cargo install abstractcore-console` |
 | **Code Web UI** | Browser client of AbstractCode (gateway-backed): workflow selector, Files tab, live replies | the gateway console's **Apps** page (served at `/apps/code/`), or `npx @abstractframework/code --gateway-url <url>` |
 | **Flow Editor** | Visual workflow authoring in the browser | the gateway console's **Apps** page (served at `/apps/flow/`), or `npx @abstractframework/flow --gateway-url <url>` |
@@ -363,7 +369,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.7.1)
+### Release matrix (abstractframework 0.8.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
@@ -372,10 +378,10 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.8.1 |
-| PyPI | `abstractassistant` | 0.10.0 |
-| PyPI | `abstractcore` | 2.20.2 |
-| PyPI | `AbstractRuntime` | 0.8.1 |
+| PyPI | `abstractgateway` | 0.10.0 |
+| PyPI | `abstractassistant` | 0.11.0 |
+| PyPI | `abstractcore` | 2.22.0 |
+| PyPI | `AbstractRuntime` | 0.8.2 |
 | PyPI | `abstractagent` | 0.3.17 |
 | PyPI | `abstractskill` | 0.3.0 |
 | PyPI | `AbstractMemory` | 0.3.0 |
@@ -384,17 +390,17 @@ and tested together.
 | PyPI | `abstractvision` | 0.3.33 |
 | PyPI | `abstractmusic` | 0.1.15 |
 | PyPI | `abstract3d` | 0.3.2 |
-| npm | `@abstractframework/flow` | 0.4.0 |
-| 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.12.0 |
-| crates.io | `abstractcore-console` | 0.5.0 |
+| npm | `@abstractframework/flow` | 0.6.0 |
+| npm | `@abstractframework/code` | 0.9.0 |
+| npm | `@abstractframework/observer` | 0.5.0 |
+| npm | `@abstractframework/continuum` | 0.6.0 |
+| npm | `@abstractframework/entity` | 0.5.0 |
+| crates.io | `abstractcode` | 0.8.0 |
+| crates.io | `abstractgateway-console` | 0.13.0 |
+| crates.io | `abstractcore-console` | 0.6.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.8.1 (`gpu-latest` / `<version>-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.20.2 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.10.0 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.22.0 |
 
 `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.7.1 → abstractframework-0.8.0}/README.md

@@ -46,9 +46,9 @@ button of gateway 0.7.1 cannot upgrade. Gateway only, apps, and version checks:
 
 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
+NVIDIA driver 580 or newer; measured install and per-capability timings on a Quadro RTX 5000 with
+Ubuntu 26.04 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),
@@ -57,7 +57,8 @@ at login (Enter = yes; an unattended install leaves it off and says how to turn
 on `127.0.0.1:8080`, and opens its web console in your browser already signed in. A first-run guide
 then sets up a local engine (Ollama, LM Studio, MLX, llama.cpp), downloads a model that fits your
 machine, and lists the apps; the gateway serves them on its own address at `/apps/<app>/`. The
-installer also builds the terminal console, `abstractgateway-console`, which runs the same guide on
+**Setup** button at the bottom of the console's sidebar runs the guide again, keeping your choices
+unless you replace them. The installer also builds the terminal console, `abstractgateway-console`, which runs the same guide on
 a server without a browser and offers itself at the end of an install over SSH
 ([Headless or remote machine](docs/install.md#headless-or-remote-machine)).
 
@@ -124,9 +125,10 @@ 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, 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))
+- Email for each user: your email address receives sign-in codes and notifications; connect your own mailbox (IMAP, Google or Microsoft) to get failed jobs, approvals and automation results by email, and let your agents use email tools when you switch them on ([Email integration](docs/guide/email-integration.md))
 - Multi-client: terminal, browser, tray, Telegram, email
-- Start on one device, continue on another
+- Start on one device, continue on another: the web console and every browser app work on phones,
+  tablets and any window size ([Phones and tablets](docs/guide/deployment-iphone.md))
 
 ```bash
 pip install abstractgateway
@@ -172,7 +174,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.8.1` and `ghcr.io/lpalbou/abstractcore-server:2.20.2`.
+`ghcr.io/lpalbou/abstractgateway:0.10.0` and `ghcr.io/lpalbou/abstractcore-server:2.22.0`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -266,6 +268,10 @@ The ecosystem, grouped by layer. Each name links to the package's repository.
 
 ### Apps and clients
 
+The gateway's web console and the five browser apps (Code Web UI, Flow Editor, Observer, Entity,
+Continuum) adapt to phones, tablets and windows of any size: drawers below 1024 px, bottom-sheet
+dialogs and touch-sized controls on phones.
+
 | App | What it does | Install |
 |---|---|---|
 | [AbstractCode](https://github.com/lpalbou/AbstractCode) | Terminal agentic dev client (Rust, on the AbstractTUI engine) — durable sessions, tool approvals, the gateway's default workflow, workspace files, live replies | `cargo install abstractcode`, or a prebuilt binary from the [GitHub release](https://github.com/lpalbou/AbstractCode/releases) |
@@ -273,7 +279,7 @@ The ecosystem, grouped by layer. Each name links to the package's repository.
 | [AbstractObserver](https://github.com/lpalbou/AbstractObserver) | Browser UI — monitor, control, and schedule gateway runs | the gateway console's **Apps** page (served at `/apps/observer/`), or `npx @abstractframework/observer --gateway-url <url>` |
 | [AbstractEntity](https://github.com/lpalbou/AbstractEntity) | Summoned-entity manager — roster, blueprint (cognition map + editing), chat drawer, live replay | the gateway console's **Apps** page (served at `/apps/entity/`), or `npx @abstractframework/entity --gateway-url <url>` |
 | [AbstractContinuum](https://github.com/lpalbou/AbstractContinuum) | Continuous iterative development and deployment console | the gateway console's **Apps** page (served at `/apps/continuum/`), or `npx @abstractframework/continuum --gateway-url <url>` |
-| **Gateway consoles** | Operator consoles for a running gateway: web at `/console` (first-run guide, Models, Engines, providers, users), terminal via `abstractgateway-console` (the same setup guide and screens, Network and Apps included, for headless hosts) | built into `abstractgateway`; built by the installer, or `cargo install abstractgateway-console` |
+| **Gateway consoles** | Operator consoles for a running gateway: web at `/console` (sidebar groups Accounts, Work, Models and System; the **Setup** button; one Accounts table of users and entities), terminal via `abstractgateway-console` (the same setup guide and screens, Network and Apps included, for headless hosts) | built into `abstractgateway`; built by the installer, or `cargo install abstractgateway-console` |
 | **Core consoles** | Consoles for AbstractCore: web at `/console` of `abstractcore serve`, terminal via `abstractcore-console` (config, Models, Engines) | built into `abstractcore`; `cargo install abstractcore-console` |
 | **Code Web UI** | Browser client of AbstractCode (gateway-backed): workflow selector, Files tab, live replies | the gateway console's **Apps** page (served at `/apps/code/`), or `npx @abstractframework/code --gateway-url <url>` |
 | **Flow Editor** | Visual workflow authoring in the browser | the gateway console's **Apps** page (served at `/apps/flow/`), or `npx @abstractframework/flow --gateway-url <url>` |
@@ -318,7 +324,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.7.1)
+### Release matrix (abstractframework 0.8.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
@@ -327,10 +333,10 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.8.1 |
-| PyPI | `abstractassistant` | 0.10.0 |
-| PyPI | `abstractcore` | 2.20.2 |
-| PyPI | `AbstractRuntime` | 0.8.1 |
+| PyPI | `abstractgateway` | 0.10.0 |
+| PyPI | `abstractassistant` | 0.11.0 |
+| PyPI | `abstractcore` | 2.22.0 |
+| PyPI | `AbstractRuntime` | 0.8.2 |
 | PyPI | `abstractagent` | 0.3.17 |
 | PyPI | `abstractskill` | 0.3.0 |
 | PyPI | `AbstractMemory` | 0.3.0 |
@@ -339,17 +345,17 @@ and tested together.
 | PyPI | `abstractvision` | 0.3.33 |
 | PyPI | `abstractmusic` | 0.1.15 |
 | PyPI | `abstract3d` | 0.3.2 |
-| npm | `@abstractframework/flow` | 0.4.0 |
-| 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.12.0 |
-| crates.io | `abstractcore-console` | 0.5.0 |
+| npm | `@abstractframework/flow` | 0.6.0 |
+| npm | `@abstractframework/code` | 0.9.0 |
+| npm | `@abstractframework/observer` | 0.5.0 |
+| npm | `@abstractframework/continuum` | 0.6.0 |
+| npm | `@abstractframework/entity` | 0.5.0 |
+| crates.io | `abstractcode` | 0.8.0 |
+| crates.io | `abstractgateway-console` | 0.13.0 |
+| crates.io | `abstractcore-console` | 0.6.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.8.1 (`gpu-latest` / `<version>-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.20.2 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.10.0 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.22.0 |
 
 `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.7.1 → abstractframework-0.8.0}/abstractframework/__init__.py

@@ -10,15 +10,15 @@ Most implementation functionality still lives in component projects.
 
 from __future__ import annotations
 
-__version__ = "0.7.1"
+__version__ = "0.8.0"
 __author__ = "Laurent-Philippe Albou"
 __license__ = "MIT"
 
 RELEASE_VERSIONS: dict[str, str] = {
-    "abstractcore": "2.20.2",
-    "abstractruntime": "0.8.1",
+    "abstractcore": "2.22.0",
+    "abstractruntime": "0.8.2",
     "abstractagent": "0.3.17",
-    "abstractgateway": "0.8.1",
+    "abstractgateway": "0.10.0",
     "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.10.0",
+    "abstractassistant": "0.11.0",
 }
 
 PACKAGE_DISTRIBUTIONS: dict[str, str] = {
@@ -45,11 +45,11 @@ PACKAGE_DISTRIBUTIONS: dict[str, str] = {
 }
 
 NPM_RELEASE_VERSIONS: dict[str, str] = {
-    "@abstractframework/flow": "0.4.0",
-    "@abstractframework/code": "0.7.0",
-    "@abstractframework/observer": "0.3.0",
-    "@abstractframework/continuum": "0.4.0",
-    "@abstractframework/entity": "0.3.0",
+    "@abstractframework/flow": "0.6.0",
+    "@abstractframework/code": "0.9.0",
+    "@abstractframework/observer": "0.5.0",
+    "@abstractframework/continuum": "0.6.0",
+    "@abstractframework/entity": "0.5.0",
 }
 
 # Terminal tools published on crates.io alongside this release (installed with `cargo install`,
@@ -58,9 +58,9 @@ NPM_RELEASE_VERSIONS: dict[str, str] = {
 # `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.12.0",
-    "abstractcore-console": "0.5.0",
-    "abstractcode": "0.7.1",
+    "abstractgateway-console": "0.13.0",
+    "abstractcore-console": "0.6.0",
+    "abstractcode": "0.8.0",
     "abstracttui": "0.6.0",
 }