abstractframework 0.5.0__tar.gz → 0.6.1__tar.gz

{abstractframework-0.5.0 → abstractframework-0.6.1}/CHANGELOG.md

@@ -4,6 +4,185 @@ All notable changes to AbstractFramework will be documented in this file.
 
 ## [Unreleased]
 
+## [0.6.1] - 2026-09-28
+
+Every terminal command lands on your PATH, AbstractCode's terminal client says how to sign in, and
+Run now explains itself the same way in every client.
+
+### Changed
+
+- **The installer puts every command line on PATH by default**, in one folder, uv's tool bin
+  directory (`~/.local/bin` on macOS and Linux, `%USERPROFILE%\.local\bin` on Windows), next to
+  `abstractgateway`:
+  - AbstractCode's terminal client, `abstractcode`, is built whenever the terminal console is, with
+    the same cargo. `--no-code-cli` (`-NoCodeCli`) skips it; a failed build never fails the install.
+    With `--no-console` it is built only when a cargo of Rust 1.87 or later already exists.
+  - The library commands come from the gateway's own environment: AbstractCore's (`abstractcore`,
+    `abstractcore-config`, `abstractcore-chat`, `abstractcore-endpoint` and its apps `summarizer`,
+    `extractor`, `judge`, `intent`, `deepsearch`, also as `abstractcore-<app>`), `abstractvoice`,
+    `abstractvoice-prefetch`, `abstractvision` and `abstractmusic`. `--no-core-cli` (`-NoCoreCli`)
+    leaves them out.
+  - A package's commands come all together or not at all: when another program already has one of
+    its names, that package is left out with a warning naming the file, and the rest installs.
+  - `--with-code-cli` and `--with-core-cli` stay accepted (they are the default now).
+  - The summary lists every command with what it does (`abstractgateway-config`: the gateway's
+    admin command). See [Commands you get](docs/install.md#commands-you-get).
+- **Signing AbstractCode's terminal client in.** The summary prints
+  `Sign in (terminal, once): abstractcode login --token <token>` with your admin token, then
+  `abstractcode`, and the way without a token on the gateway's computer,
+  `abstractgateway apps tui-command code`. The installer never saves the token for you. Started
+  without a sign-in, `abstractcode` 0.7.1 says so and prints the same lines instead of opening
+  with an empty workflow.
+- **Terminal apps share one folder with the gateway** (AbstractGateway 0.7.1). The console's
+  **Apps** page installs and updates `abstractcode` in the same folder as the installer, so it runs
+  by name. A re-run of the installer keeps an `abstractcode` newer than its pin. On Windows,
+  `install.ps1` builds `abstractgateway-console` and `abstractcode` into `%USERPROFILE%\.local\bin`
+  (an existing copy in `%USERPROFILE%\.cargo\bin` is left in place).
+- **Uninstall** removes `abstractcode` like the console, and also the copy older gateways put in
+  `<data dir>/apps/bin` (removing that folder when it is empty; other files there are kept).
+
+### Added
+
+- **Run now reads the same everywhere** (ui-kit 0.1.16, Observer 0.2.1, Assistant 0.9.1,
+  AbstractCode terminal 0.7.1 and web 0.6.1). Every client draws Run now with the same play-in-a-circle icon and explains
+  it with the same text: it runs the automation once now instead of waiting; the next scheduled run
+  keeps its time (or starts right after this run if its time comes first); it does not count toward
+  a run limit; it works while paused, which stays paused; and it is not available while a run is in
+  progress. Pause, Resume, Stop, Edit, Archive and Discuss carry the same kind of hint. See
+  [Automations](docs/automations.md).
+
+### Changed (pins)
+
+- **abstractgateway 0.7.1** (was 0.7.0): terminal apps in the uv tool bin folder.
+- **abstractassistant 0.9.1** (was 0.9.0): the shared Run now icon and hints.
+- npm: **@abstractframework/observer 0.2.1** and **@abstractframework/code 0.6.1** (both with the
+  shared Run now hints, ui-kit 0.1.16).
+- crates.io: **abstractcode 0.7.1** (sign-in report, "not signed in" state, Run now line).
+- Unchanged: abstractcore 2.18.0, AbstractRuntime 0.7.1, abstractagent 0.3.17, abstractvoice 0.13.0,
+  abstractskill 0.3.0, AbstractMemory 0.3.0, abstractsemantics 0.0.5, abstractvision 0.3.30,
+  abstractmusic 0.1.15, flow 0.4.0, continuum 0.4.0, entity 0.3.0, `abstractgateway-console` 0.11.0,
+  `abstractcore-console` 0.4.0 and `abstracttui` 0.6.0.
+
+## [0.6.0] - 2026-09-28
+
+Remote and headless machines work like a Mac: one address and one SSH tunnel reach the console, the
+API and every browser app; every client finds the local gateway on its own; AbstractCode creates and
+runs automations; history replay keeps whole messages up to 50,000 tokens and never cuts one.
+
+### Added
+
+- **Browser apps open through the gateway at `/apps/<app>/`** (AbstractGateway 0.7.0). Flow, Code,
+  Observer, Continuum and Entity are served on the gateway's own address (HTTP, server-sent events
+  and WebSocket), signed in with the app's gateway session, so a LAN address, a reverse proxy or one
+  SSH tunnel reaches them all. The apps listen on `127.0.0.1` by default. The installer summary's
+  `Apps:` line and the docs point to `<gateway>/apps/<app>/`; the console's **Apps** page installs
+  and opens them. Running an app on its own with `npx … --gateway-url <url>` is the advanced
+  alternative (`Standalone:` line).
+- **Local gateway pointer.** After the health check the installer writes
+  `~/.abstractframework/gateway.json` (Windows: `%USERPROFILE%\.abstractframework\gateway.json`),
+  mode 0600: the gateway's loopback URL, port and data directory, never a token. The Assistant (the
+  macOS app included), both terminal consoles, AbstractCode's terminal client and the browser apps'
+  servers read it to find a gateway on a port other than 8080, and follow it when the gateway moves.
+  The installer writes it for the install it just made, a custom `--data-dir` included (replacing a
+  pointer that names another data directory); `abstractgateway serve` then keeps it current under
+  its ownership rule. The uninstaller deletes it when it names the uninstalled data directory.
+- **Automations in AbstractCode** (`abstractcode` 0.7.0, `@abstractframework/code` 0.6.0). In the
+  terminal client, `/automations` lists and opens automations (runs as chat pairs, waits that need
+  you, the folder, pause/resume, run now, stop, revise, archive, Discuss) and `/schedule` creates
+  one; the browser client has the same in its **Automations** sidebar section. See
+  [Automations](docs/automations.md).
+- **Start at login from the consoles.** Both the web console (Gateway card, last setup step) and the
+  terminal console (F3, the Finish step) have a **Start at login** switch that changes the login item
+  without restarting the gateway.
+- **The terminal console on a headless machine** (`abstractgateway-console` 0.11.0): a Network
+  screen that shows the saved and the running setting and offers the restart, Apps that give the link
+  and the tunnel command instead of opening a browser, voice and engine states, and the local
+  gateway pointer. Neither terminal console tries to open a browser on a machine without a display.
+- `--ask-wait SECONDS` (Windows: `-AskWait`) sets how long a timed question waits (default 25, at
+  most 25). `--console-wait` remains as an alias.
+
+### Changed
+
+- **One flag for the gateway address: `--gateway-url`** in every app and terminal client
+  (`--url` for the gateway terminal console and `--gateway` for AbstractCode remain as aliases). The
+  installer summary and the docs use it; with `--with-apps` the installer prints
+  `npx -y @abstractframework/<app>@<version> --gateway-url <gateway>` for all five apps.
+- **Start at login is asked whenever a person is at a terminal**, not only with `--interactive`:
+  `curl … | sh` asks it on your terminal (`/dev/tty`), Enter = yes. Nobody answering within
+  `--ask-wait`, an install without a terminal (a script, CI, a provisioning tool) and `--yes` keep
+  the previous choice on a re-run and leave start at login **off** on a first install (it was on);
+  the summary then says how to turn it on: the **Start at login** switch in either console, or
+  `abstractgateway service enable`. A re-run reads the login item's own state, so a change made
+  with a console's switch is kept. `install.ps1` asks the same question on an interactive console
+  (it registered the login entry without asking). `--interactive` waits for answers without a time
+  limit; `--no-service` still asks nothing.
+- **On a remote or headless session** (SSH, or Linux without a display) with a terminal, the
+  installer offers the terminal console at the end ("Press Enter within 25 s"), signed in; nobody answering skips it, so automation never blocks.
+  Over SSH it no longer opens a browser on the remote machine. `--no-open` skips both.
+- **History replay keeps whole messages up to 50,000 tokens** (AbstractRuntime 0.7.0): growing
+  automations, session chats, run chat, the docs assistants and entity visits replay the newest whole
+  turns up to 50,000 tokens. No message is cut; the former 40-message, 24,000-character and
+  per-message caps are gone. Each run records how many earlier messages were not replayed, and the
+  clients say so.
+- **Voice says what it can do** (AbstractVoice 0.13.0, AbstractCore 2.18.0). Voice listings name
+  the providers that cannot run here and why, instead of an empty list; cloud voice providers are
+  listed as needing a key until one is configured; a capability route whose engine is not installed
+  reports `engine_missing` with the install command; an OpenAI key saved in the Providers screen
+  reaches voice. The installer adds local voice to every install profile: Supertonic text-to-speech
+  and Whisper speech-to-text (`abstractvoice[supertonic,stt]`), both CPU, from prebuilt wheels
+  (skipped where no wheels exist: musl Linux / Alpine, macOS before 13; Whisper on Windows ARM64).
+  Voice never fails an install: where its packages do not install the gateway is installed without
+  it. The summary's `Voice:` line says what was installed, and a re-run that adds voice restarts the
+  gateway to load it.
+- **Observer: Edit opens the form, and a calmer Automations page** (`@abstractframework/observer`
+  0.2.0). A row's **Edit** opens the automation's edit form at once, prefilled (title, task,
+  interval, context, tools); action buttons carry icons; a workspace folder can be browsed from the
+  browser; **Discuss** opens a chat with a fork of the automation; a run's **Ask** chat sends the
+  whole conversation.
+- **Apple silicon model fits account for the GPU memory limit** (AbstractCore 2.18.0): a model that
+  fits once macOS raises its limit reads `needs_gpu_limit` with the exact command.
+
+### Security
+
+- **DNS-rebinding protection in the browser apps**: an app treats a browser as on this machine only
+  when both its address and the page's host are loopback, so a rebinding page can neither reveal a
+  folder nor change the gateway address. Continuum's local-only pages answer on `localhost` or
+  `127.0.0.1` only. The gateway's app proxy refuses requests with another origin or an invalid host.
+- **Server-held keys are spent only for authenticated requests** (AbstractCore 2.18.0): with a
+  saved or environment OpenAI key, unauthenticated requests to the AbstractVoice audio routes, the
+  audio and vision discovery routes, OpenAI-backed vision generation and the capability discovery
+  routes get `401`, also with `ABSTRACTCORE_SERVER_ALLOW_UNAUTHENTICATED=1`; an explicit
+  `X-AbstractCore-Provider-API-Key` is spent instead. The music route follows the same rule while
+  the server holds a music backend key.
+- The local gateway pointer is written without following links, with mode 0600, and readers reject
+  a pointer that other users can write.
+
+### Changed (pins)
+
+- **abstractgateway 0.7.0** (was 0.6.0): apps through `/apps/<app>/`, the local gateway pointer,
+  start at login from the consoles, cloud voice providers listed, the history window on every chat
+  route, and the terminal console 0.11.0.
+- **abstractcore 2.18.0** (was 2.17.0): `engine_missing`, `needs_gpu_limit`, the saved OpenAI key
+  for voice, the key guards above, and `abstractcore-console` 0.4.0.
+- **AbstractRuntime 0.7.1** (was 0.6.0): the 50,000-token history window, recorded in each run;
+  images in replayed history stay images, and an image counts as a flat 512 tokens in the window.
+  Library callers of `session_chat_messages` and `automation_timeline_messages` should read its
+  changelog's Breaking note.
+- **abstractagent 0.3.17** (was 0.3.16): ReAct sends the runtime's history window when the host
+  asks for it.
+- **abstractvoice 0.13.0** (was 0.12.0): engine status and unavailable-provider reasons, Qwen3-ASR
+  on Transformers 5.x, Qwen3-TTS predictor and sampler flags.
+- **abstractassistant 0.9.0** (was 0.8.0): the macOS app finds a gateway through the local gateway
+  pointer; automation cards say their state in words.
+- npm: **@abstractframework/flow 0.4.0**, **code 0.6.0**, **observer 0.2.0**, **continuum 0.4.0**
+  and **entity 0.3.0**, all served through the gateway at `/apps/<app>/` and taking
+  `--gateway-url`.
+- crates.io: **abstractgateway-console 0.11.0**, **abstractcore-console 0.4.0** and
+  **abstractcode 0.7.0**.
+- The pins apply to the base install and to the `apple` / `gpu` extras. Unchanged:
+  abstractskill 0.3.0, AbstractMemory 0.3.0, abstractsemantics 0.0.5, abstractvision 0.3.30,
+  abstractmusic 0.1.15 and `abstracttui` 0.6.0.
+
 ## [0.5.0] - 2026-09-27
 
 Automations, a terminal console installed by default, and a headless setup path: installing and

{abstractframework-0.5.0/abstractframework.egg-info → abstractframework-0.6.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstractframework
-Version: 0.5.0
+Version: 0.6.1
 Summary: Unified installer and documentation hub for the AbstractFramework ecosystem
 Author-email: Laurent-Philippe Albou <contact@abstractframework.ai>
 License: MIT
@@ -23,23 +23,23 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: abstractgateway==0.6.0
-Requires-Dist: abstractassistant==0.8.0
-Requires-Dist: abstractcore==2.17.0
-Requires-Dist: AbstractRuntime==0.6.0
-Requires-Dist: abstractagent==0.3.16
+Requires-Dist: abstractgateway==0.7.1
+Requires-Dist: abstractassistant==0.9.1
+Requires-Dist: abstractcore==2.18.0
+Requires-Dist: AbstractRuntime==0.7.1
+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.12.0
+Requires-Dist: abstractvoice==0.13.0
 Requires-Dist: abstractvision==0.3.30
 Requires-Dist: abstractmusic==0.1.15
 Provides-Extra: apple
-Requires-Dist: abstractgateway[apple]==0.6.0; extra == "apple"
-Requires-Dist: abstractassistant[apple]==0.8.0; platform_system == "Darwin" and extra == "apple"
+Requires-Dist: abstractgateway[apple]==0.7.1; extra == "apple"
+Requires-Dist: abstractassistant[apple]==0.9.1; platform_system == "Darwin" and extra == "apple"
 Provides-Extra: gpu
-Requires-Dist: abstractgateway[gpu]==0.6.0; extra == "gpu"
-Requires-Dist: abstractassistant[gpu]==0.8.0; extra == "gpu"
+Requires-Dist: abstractgateway[gpu]==0.7.1; extra == "gpu"
+Requires-Dist: abstractassistant[gpu]==0.9.1; extra == "gpu"
 Dynamic: license-file
 
 # AbstractFramework
@@ -64,11 +64,14 @@ Think of it as an **agentic OS**: durable runs + replay-first observability + mu
 ## Quick start
 
 The installer sets up the gateway in your user account (no admin password, no system Python),
-asks whether to start it at login, starts it 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 installer also
-builds the terminal console, `abstractgateway-console`, which runs the same guide on a server without
-a browser ([Headless or remote machine](docs/install.md#headless-or-remote-machine)).
+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
+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
+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)).
 
 - **Mac, no Terminal:** download and double-click
   [AbstractFramework-Installer.pkg](https://github.com/lpalbou/AbstractFramework/releases/latest/download/AbstractFramework-Installer.pkg).
@@ -78,7 +81,7 @@ a browser ([Headless or remote machine](docs/install.md#headless-or-remote-machi
 - **macOS / Linux, one line:**
 
   ```bash
-  curl -LsSf https://raw.githubusercontent.com/lpalbou/AbstractFramework/main/scripts/install.sh | sh -s -- --interactive
+  curl -LsSf https://raw.githubusercontent.com/lpalbou/AbstractFramework/main/scripts/install.sh | sh
   ```
 
 - **Windows 10 22H2+ / 11** (PowerShell):
@@ -160,7 +163,8 @@ With no auth configured, `abstractgateway serve` binds `127.0.0.1:8080`, enables
 creates `default/admin` in the per-user data folder, and prints a one-time sign-in link
 (`http://127.0.0.1:8080/console#claim=…`, valid 10 minutes, this machine only). Open it to reach the
 web console and its first-run guide. `abstractgateway claim` mints a new link;
-`abstractgateway service install` starts the gateway at login.
+`abstractgateway service enable` (or the console's **Start at login** switch) starts the gateway at
+login.
 
 Browser apps on `http://localhost:*` and `http://127.0.0.1:*` may always call it. To choose
 another data folder or allow another browser origin:
@@ -182,17 +186,19 @@ AbstractFlow, AbstractCode Web or AbstractObserver, or to the console without a
 `ABSTRACTGATEWAY_AUTH_TOKEN` remains a legacy server/operator bearer token; it is not a browser
 sign-in token.
 
-Monitor runs from a browser, or from a terminal with the gateway console:
+Monitor runs from a browser, or from a terminal with the gateway console. The console's **Apps**
+page installs and opens the browser apps, served by the gateway at `/apps/<app>/`
+(`http://127.0.0.1:8080/apps/observer/`), so one address (and one SSH tunnel) reaches them all:
 
 ```bash
-npx @abstractframework/observer   # open http://localhost:3001
+npx @abstractframework/observer --gateway-url http://127.0.0.1:8080   # or run one on its own
 
 cargo install abstractgateway-console   # Rust 1.87+; the installer builds it for you
-abstractgateway-console --url http://127.0.0.1:8080 --token <admin token>   # <data dir>/auth/bootstrap-admin-token
+abstractgateway-console --gateway-url http://127.0.0.1:8080 --token <admin token>   # <data dir>/auth/bootstrap-admin-token
 ```
 
 Container images are published for the gateway and the AbstractCore server:
-`ghcr.io/lpalbou/abstractgateway:0.6.0` and `ghcr.io/lpalbou/abstractcore-server:2.17.0`.
+`ghcr.io/lpalbou/abstractgateway:0.7.1` and `ghcr.io/lpalbou/abstractcore-server:2.18.0`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -230,7 +236,7 @@ See [Agent sessions](docs/agent-sessions.md).
 
 AbstractFlow lets you author complex agentic orchestration as portable `.flow` bundles:
 
-1. Open the Flow Editor (`npx @abstractframework/flow`)
+1. Open the Flow Editor (the console's **Apps** page, or `npx @abstractframework/flow --gateway-url <url>`)
 2. Build a workflow: LLM steps, tool steps, branching, loops, subflows
 3. Export a `.flow` bundle into your own bundle directory and point `ABSTRACTGATEWAY_FLOWS_DIR` at it (or publish it through the Gateway API)
 4. Run it from any gateway-backed client (Observer, AbstractAssistant, Code Web UI, your app)
@@ -290,13 +296,13 @@ The ecosystem, grouped by layer. Each name links to the package's repository.
 |---|---|---|
 | [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) |
 | [AbstractAssistant](https://github.com/lpalbou/AbstractAssistant) | macOS tray client — gateway-native, follows the gateway's default workflow or your pick, live replies, voice support | `pip install abstractassistant`, or **Open** in the gateway console (starts it signed in) |
-| [AbstractObserver](https://github.com/lpalbou/AbstractObserver) | Browser UI — monitor, control, and schedule gateway runs | `npx @abstractframework/observer` |
-| [AbstractEntity](https://github.com/lpalbou/AbstractEntity) | Summoned-entity manager — roster, blueprint (cognition map + editing), chat drawer, live replay | `npx @abstractframework/entity` |
-| [AbstractContinuum](https://github.com/lpalbou/AbstractContinuum) | Continuous iterative development and deployment console | `npx @abstractframework/continuum` |
-| **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 twelve screens, for headless hosts) | built into `abstractgateway`; built by the installer, or `cargo install abstractgateway-console` |
+| [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` |
 | **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 | `npx @abstractframework/code` |
-| **Flow Editor** | Visual workflow authoring in the browser | `npx @abstractframework/flow` |
+| **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>` |
 
 ### Shared libraries
 
@@ -338,7 +344,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 / Windows with a CUDA or ROCm GPU | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
 
-### Release matrix (abstractframework 0.5.0)
+### Release matrix (abstractframework 0.6.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
@@ -347,28 +353,28 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.6.0 |
-| PyPI | `abstractassistant` | 0.8.0 |
-| PyPI | `abstractcore` | 2.17.0 |
-| PyPI | `AbstractRuntime` | 0.6.0 |
-| PyPI | `abstractagent` | 0.3.16 |
+| PyPI | `abstractgateway` | 0.7.1 |
+| PyPI | `abstractassistant` | 0.9.1 |
+| PyPI | `abstractcore` | 2.18.0 |
+| PyPI | `AbstractRuntime` | 0.7.1 |
+| PyPI | `abstractagent` | 0.3.17 |
 | PyPI | `abstractskill` | 0.3.0 |
 | PyPI | `AbstractMemory` | 0.3.0 |
 | PyPI | `abstractsemantics` | 0.0.5 |
-| PyPI | `abstractvoice` | 0.12.0 |
+| PyPI | `abstractvoice` | 0.13.0 |
 | PyPI | `abstractvision` | 0.3.30 |
 | PyPI | `abstractmusic` | 0.1.15 |
-| npm | `@abstractframework/flow` | 0.3.22 |
-| npm | `@abstractframework/code` | 0.5.0 |
-| npm | `@abstractframework/observer` | 0.1.14 |
-| npm | `@abstractframework/continuum` | 0.3.2 |
-| npm | `@abstractframework/entity` | 0.2.2 |
-| crates.io | `abstractcode` | 0.6.0 |
-| crates.io | `abstractgateway-console` | 0.10.0 |
-| crates.io | `abstractcore-console` | 0.3.0 |
+| npm | `@abstractframework/flow` | 0.4.0 |
+| npm | `@abstractframework/code` | 0.6.1 |
+| npm | `@abstractframework/observer` | 0.2.1 |
+| npm | `@abstractframework/continuum` | 0.4.0 |
+| npm | `@abstractframework/entity` | 0.3.0 |
+| crates.io | `abstractcode` | 0.7.1 |
+| crates.io | `abstractgateway-console` | 0.11.0 |
+| crates.io | `abstractcore-console` | 0.4.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.6.0 (`gpu-latest` / `<version>-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.17.0 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.7.1 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.18.0 |
 
 Optional add-ons that are not part of any profile install separately:
 `pip install abstract3d` (0.3.1) and `pip install abstractcamera` (0.2.0). `abstractskill` (pinned above)

{abstractframework-0.5.0 → abstractframework-0.6.1}/README.md

@@ -20,11 +20,14 @@ Think of it as an **agentic OS**: durable runs + replay-first observability + mu
 ## Quick start
 
 The installer sets up the gateway in your user account (no admin password, no system Python),
-asks whether to start it at login, starts it 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 installer also
-builds the terminal console, `abstractgateway-console`, which runs the same guide on a server without
-a browser ([Headless or remote machine](docs/install.md#headless-or-remote-machine)).
+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
+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
+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)).
 
 - **Mac, no Terminal:** download and double-click
   [AbstractFramework-Installer.pkg](https://github.com/lpalbou/AbstractFramework/releases/latest/download/AbstractFramework-Installer.pkg).
@@ -34,7 +37,7 @@ a browser ([Headless or remote machine](docs/install.md#headless-or-remote-machi
 - **macOS / Linux, one line:**
 
   ```bash
-  curl -LsSf https://raw.githubusercontent.com/lpalbou/AbstractFramework/main/scripts/install.sh | sh -s -- --interactive
+  curl -LsSf https://raw.githubusercontent.com/lpalbou/AbstractFramework/main/scripts/install.sh | sh
   ```
 
 - **Windows 10 22H2+ / 11** (PowerShell):
@@ -116,7 +119,8 @@ With no auth configured, `abstractgateway serve` binds `127.0.0.1:8080`, enables
 creates `default/admin` in the per-user data folder, and prints a one-time sign-in link
 (`http://127.0.0.1:8080/console#claim=…`, valid 10 minutes, this machine only). Open it to reach the
 web console and its first-run guide. `abstractgateway claim` mints a new link;
-`abstractgateway service install` starts the gateway at login.
+`abstractgateway service enable` (or the console's **Start at login** switch) starts the gateway at
+login.
 
 Browser apps on `http://localhost:*` and `http://127.0.0.1:*` may always call it. To choose
 another data folder or allow another browser origin:
@@ -138,17 +142,19 @@ AbstractFlow, AbstractCode Web or AbstractObserver, or to the console without a
 `ABSTRACTGATEWAY_AUTH_TOKEN` remains a legacy server/operator bearer token; it is not a browser
 sign-in token.
 
-Monitor runs from a browser, or from a terminal with the gateway console:
+Monitor runs from a browser, or from a terminal with the gateway console. The console's **Apps**
+page installs and opens the browser apps, served by the gateway at `/apps/<app>/`
+(`http://127.0.0.1:8080/apps/observer/`), so one address (and one SSH tunnel) reaches them all:
 
 ```bash
-npx @abstractframework/observer   # open http://localhost:3001
+npx @abstractframework/observer --gateway-url http://127.0.0.1:8080   # or run one on its own
 
 cargo install abstractgateway-console   # Rust 1.87+; the installer builds it for you
-abstractgateway-console --url http://127.0.0.1:8080 --token <admin token>   # <data dir>/auth/bootstrap-admin-token
+abstractgateway-console --gateway-url http://127.0.0.1:8080 --token <admin token>   # <data dir>/auth/bootstrap-admin-token
 ```
 
 Container images are published for the gateway and the AbstractCore server:
-`ghcr.io/lpalbou/abstractgateway:0.6.0` and `ghcr.io/lpalbou/abstractcore-server:2.17.0`.
+`ghcr.io/lpalbou/abstractgateway:0.7.1` and `ghcr.io/lpalbou/abstractcore-server:2.18.0`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -186,7 +192,7 @@ See [Agent sessions](docs/agent-sessions.md).
 
 AbstractFlow lets you author complex agentic orchestration as portable `.flow` bundles:
 
-1. Open the Flow Editor (`npx @abstractframework/flow`)
+1. Open the Flow Editor (the console's **Apps** page, or `npx @abstractframework/flow --gateway-url <url>`)
 2. Build a workflow: LLM steps, tool steps, branching, loops, subflows
 3. Export a `.flow` bundle into your own bundle directory and point `ABSTRACTGATEWAY_FLOWS_DIR` at it (or publish it through the Gateway API)
 4. Run it from any gateway-backed client (Observer, AbstractAssistant, Code Web UI, your app)
@@ -246,13 +252,13 @@ The ecosystem, grouped by layer. Each name links to the package's repository.
 |---|---|---|
 | [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) |
 | [AbstractAssistant](https://github.com/lpalbou/AbstractAssistant) | macOS tray client — gateway-native, follows the gateway's default workflow or your pick, live replies, voice support | `pip install abstractassistant`, or **Open** in the gateway console (starts it signed in) |
-| [AbstractObserver](https://github.com/lpalbou/AbstractObserver) | Browser UI — monitor, control, and schedule gateway runs | `npx @abstractframework/observer` |
-| [AbstractEntity](https://github.com/lpalbou/AbstractEntity) | Summoned-entity manager — roster, blueprint (cognition map + editing), chat drawer, live replay | `npx @abstractframework/entity` |
-| [AbstractContinuum](https://github.com/lpalbou/AbstractContinuum) | Continuous iterative development and deployment console | `npx @abstractframework/continuum` |
-| **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 twelve screens, for headless hosts) | built into `abstractgateway`; built by the installer, or `cargo install abstractgateway-console` |
+| [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` |
 | **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 | `npx @abstractframework/code` |
-| **Flow Editor** | Visual workflow authoring in the browser | `npx @abstractframework/flow` |
+| **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>` |
 
 ### Shared libraries
 
@@ -294,7 +300,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 / Windows with a CUDA or ROCm GPU | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
 
-### Release matrix (abstractframework 0.5.0)
+### Release matrix (abstractframework 0.6.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
@@ -303,28 +309,28 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.6.0 |
-| PyPI | `abstractassistant` | 0.8.0 |
-| PyPI | `abstractcore` | 2.17.0 |
-| PyPI | `AbstractRuntime` | 0.6.0 |
-| PyPI | `abstractagent` | 0.3.16 |
+| PyPI | `abstractgateway` | 0.7.1 |
+| PyPI | `abstractassistant` | 0.9.1 |
+| PyPI | `abstractcore` | 2.18.0 |
+| PyPI | `AbstractRuntime` | 0.7.1 |
+| PyPI | `abstractagent` | 0.3.17 |
 | PyPI | `abstractskill` | 0.3.0 |
 | PyPI | `AbstractMemory` | 0.3.0 |
 | PyPI | `abstractsemantics` | 0.0.5 |
-| PyPI | `abstractvoice` | 0.12.0 |
+| PyPI | `abstractvoice` | 0.13.0 |
 | PyPI | `abstractvision` | 0.3.30 |
 | PyPI | `abstractmusic` | 0.1.15 |
-| npm | `@abstractframework/flow` | 0.3.22 |
-| npm | `@abstractframework/code` | 0.5.0 |
-| npm | `@abstractframework/observer` | 0.1.14 |
-| npm | `@abstractframework/continuum` | 0.3.2 |
-| npm | `@abstractframework/entity` | 0.2.2 |
-| crates.io | `abstractcode` | 0.6.0 |
-| crates.io | `abstractgateway-console` | 0.10.0 |
-| crates.io | `abstractcore-console` | 0.3.0 |
+| npm | `@abstractframework/flow` | 0.4.0 |
+| npm | `@abstractframework/code` | 0.6.1 |
+| npm | `@abstractframework/observer` | 0.2.1 |
+| npm | `@abstractframework/continuum` | 0.4.0 |
+| npm | `@abstractframework/entity` | 0.3.0 |
+| crates.io | `abstractcode` | 0.7.1 |
+| crates.io | `abstractgateway-console` | 0.11.0 |
+| crates.io | `abstractcore-console` | 0.4.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.6.0 (`gpu-latest` / `<version>-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.17.0 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.7.1 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.18.0 |
 
 Optional add-ons that are not part of any profile install separately:
 `pip install abstract3d` (0.3.1) and `pip install abstractcamera` (0.2.0). `abstractskill` (pinned above)

{abstractframework-0.5.0 → abstractframework-0.6.1}/abstractframework/__init__.py

@@ -10,22 +10,22 @@ Most implementation functionality still lives in component projects.
 
 from __future__ import annotations
 
-__version__ = "0.5.0"
+__version__ = "0.6.1"
 __author__ = "Laurent-Philippe Albou"
 __license__ = "MIT"
 
 RELEASE_VERSIONS: dict[str, str] = {
-    "abstractcore": "2.17.0",
-    "abstractruntime": "0.6.0",
-    "abstractagent": "0.3.16",
-    "abstractgateway": "0.6.0",
+    "abstractcore": "2.18.0",
+    "abstractruntime": "0.7.1",
+    "abstractagent": "0.3.17",
+    "abstractgateway": "0.7.1",
     "abstractskill": "0.3.0",
     "abstractmemory": "0.3.0",
     "abstractsemantics": "0.0.5",
-    "abstractvoice": "0.12.0",
+    "abstractvoice": "0.13.0",
     "abstractvision": "0.3.30",
     "abstractmusic": "0.1.15",
-    "abstractassistant": "0.8.0",
+    "abstractassistant": "0.9.1",
 }
 
 PACKAGE_DISTRIBUTIONS: dict[str, str] = {
@@ -43,19 +43,19 @@ PACKAGE_DISTRIBUTIONS: dict[str, str] = {
 }
 
 NPM_RELEASE_VERSIONS: dict[str, str] = {
-    "@abstractframework/flow": "0.3.22",
-    "@abstractframework/code": "0.5.0",
-    "@abstractframework/observer": "0.1.14",
-    "@abstractframework/continuum": "0.3.2",
-    "@abstractframework/entity": "0.2.2",
+    "@abstractframework/flow": "0.4.0",
+    "@abstractframework/code": "0.6.1",
+    "@abstractframework/observer": "0.2.1",
+    "@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 by default, abstractcode with --with-code-cli).
+# or by the bootstrap scripts: the gateway console and abstractcode by default).
 CRATE_RELEASE_VERSIONS: dict[str, str] = {
-    "abstractgateway-console": "0.10.0",
-    "abstractcore-console": "0.3.0",
-    "abstractcode": "0.6.0",
+    "abstractgateway-console": "0.11.0",
+    "abstractcore-console": "0.4.0",
+    "abstractcode": "0.7.1",
     "abstracttui": "0.6.0",
 }
 

{abstractframework-0.5.0 → abstractframework-0.6.1}/abstractframework/install_manifest.py

@@ -38,10 +38,14 @@ BOOTSTRAP_FLAGS: list[dict[str, str]] = [
      "summary": "Skip the terminal console. By default abstractgateway-console is built "
                 "with cargo (install.sh adds Rust through rustup when cargo is missing; "
                 "needs a C compiler)."},
-    {"sh": "--with-code-cli", "ps": "-WithCodeCli", "env": "",
-     "summary": "cargo install abstractcode (terminal client) when cargo exists."},
-    {"sh": "--with-core-cli", "ps": "-WithCoreCli", "env": "",
-     "summary": "Also expose the abstractcore command (--with-executables-from abstractcore)."},
+    {"sh": "--no-code-cli", "ps": "-NoCodeCli", "env": "",
+     "summary": "Skip AbstractCode's terminal client. By default abstractcode is built with "
+                "the terminal console's cargo, into the same folder (--with-code-cli, the "
+                "old opt-in, is accepted)."},
+    {"sh": "--no-core-cli", "ps": "-NoCoreCli", "env": "",
+     "summary": "Do not expose AbstractCore's commands (abstractcore, its apps) and "
+                "abstractvoice, abstractvision, abstractmusic next to the gateway's "
+                "(--with-core-cli, the old opt-in, is accepted)."},
     {"sh": "--with-ollama", "ps": "-WithOllama", "env": "",
      "summary": "Run Ollama's official installer (Linux/macOS may ask for sudo)."},
     {"sh": "--with-lmstudio", "ps": "-WithLmStudio", "env": "",
@@ -50,7 +54,8 @@ BOOTSTRAP_FLAGS: list[dict[str, str]] = [
     {"sh": "--no-service", "ps": "-NoService", "env": "",
      "summary": "Do not register a login service; start the gateway in the background."},
     {"sh": "--no-start", "ps": "-NoStart", "env": "", "summary": "Install only."},
-    {"sh": "--no-open", "ps": "-NoOpen", "env": "", "summary": "Do not open the browser."},
+    {"sh": "--no-open", "ps": "-NoOpen", "env": "",
+     "summary": "Do not open the browser (on a remote or headless session: do not open the terminal console)."},
     {"sh": "--print", "ps": "-Print", "env": "",
      "summary": "Dry run: preflight, then print every command; change nothing."},
     {"sh": "--uninstall [--purge]", "ps": "-Uninstall [-Purge]", "env": "",