OpenAgent v1.1.0-beta.19

Product beta 19 registers Claude/Codex proxy media capabilities from the exact /v1/models catalog when adding a model through the standalone server. Core beta 10 carries the fields through discovery. Explicit model settings remain authoritative; unreachable providers do not receive guessed media support.

Nine coordinated product wheels and a release manifest are attached. Framework wheel SHA-256: 31a8951f3610cbd0ae3ac1d8b1a8f693461b56b3d3f8ac72f7b8c31ab03ead76; manifest SHA-256: ea9e9e8ee1445f91d13fbb3e720f00acbc16077bb20b8b0eb5bcecc048b3b636. Source commit: 2e6801850abac8e25e0fa9e2e81653a018dca25f.

Core public suite: 137 tests and 23 subtests passed. Focused product registration test passed. The legacy full product test collector remains blocked by an existing openagent_server.models import in test_inplace_recovery.

OpenAgent v1.1.0-beta.18

Updates the coordinated Python product stack to Core beta 9. Fixes Claude proxy vision capability inference for newly registered models. Friday and Mixout persisted model metadata were updated after direct proxy image tests and verified SQLite backups. Friday Telegram photo to Claude Opus to reply succeeded in run fb1a5c96-eb0c-45cb-8ea4-c067041ee9b5. Desktop App code is unchanged.

OpenAgent server v1.1.0-beta.17

OpenAgent server v1.1.0-beta.17: private Telegram vault access

The standalone server can explicitly grant its owner access to the agent vault
through a verified Telegram bridge. The bridge has a separate technical
principal, so owner-only vault policy previously hid vault and vault-gate
from private Telegram turns even while both MCP processes were healthy.

Configure the exact owner sender ID in both places:

channels:
  telegram:
    allowed_users: ["<owner Telegram numeric ID>"]
runtime_tool_audiences:
  vault_owner_channels:
    telegram: ["<owner Telegram numeric ID>"]

The grant applies only when a live, private tg:<ID> turn is authenticated as
the Telegram bridge and both allowlists contain the same ID. It also covers
vault-gate and vault note reads in native memory authorization. It does not
apply to WhatsApp, other Telegram senders, shared conversations, or deferred
work. The existing runtime_tool_audiences.vault: installation policy retains
its separate, broader meaning.

This is a server-wheel update over the beta 16 product dependency set. Core,
Tools, CLI and App code are unchanged.

Friday deployment and live acceptance, 3 October 2026

• The change was pushed to main at 2ff842925542b88307924dbb78bfa574b4e454b4 and the beta 17 release contains openagent_framework-1.1.0b17-py3-none-any.whl (SHA-256 978f8a88521ed94821f5ad151374e9efc1d7cd3160a7ddb79f10eb4b19880717). The installed wheel's unchanged beta 16 dependency set passed uv pip check across 149 packages and openagent selfcheck.
• Friday on Bluehost runs /srv/friday/releases/v1.1.0-beta.17/venv through openagent-friday.service. The configuration grants vault access only to the existing allowlisted Telegram sender. Before switching, /srv/friday/backups/pre-beta17-20261003T135613Z captured the config and a SQLite backup whose integrity_check returned ok. The Telegram and WhatsApp bridges, vault (15 tools), and vault-gate (12 tools) reconnected; the service remained active with zero automatic restarts.
• A live message from the signed-in Telegram client asked Friday to discover vault and read a note without publishing its contents. Discovery showed the vault. The first path, access.md, did not exist; vault_read_note correctly returned a file-not-found error, although Friday initially described that result too optimistically. A corrective Telegram turn read the existing _index.md; the durable vault_read_note invocation returned success, run 788ac852-6ae9-42ed-a02a-5894d5a9e605 completed successfully, and Friday replied VAULT READ OK without disclosing the note. This verifies the Telegram bridge identity, discovery, authorized invocation and channel reply together.

OpenAgent v1.1.0-beta.16

OpenAgent 1.1.0b16 is the corrected server/CLI wheel release for Telegram voice. It includes the shared Core 1.1.0b8 STT handoff and Telegram audio-file transcription from beta 15. It also constrains PyAV below 19: PyAV 19 removed metadata_errors from av.open(), which caused faster-whisper 1.2.1 to return no transcript on Friday. The original voice attachment remains in the session; the chat model receives text.

Nine Python product wheels and their SHA-256 source manifest were built from clean commit 7aca695. A fresh Python 3.12 install resolved PyAV 18.1.0 and faster-whisper 1.2.1, passed dependency checks across 142 packages, openagent selfcheck, and 18 CLI packaging tests. A real Italian OGG/Opus fixture transcribed correctly. The Core public suite passed 133 tests plus 23 subtests. Desktop code is unchanged; the latest desktop App remains beta 14. Live host and Telegram reply acceptance are recorded separately.

OpenAgent v1.1.0-beta.15

Superseded by v1.1.0-beta.16. Beta 15 did not constrain PyAV; PyAV 19 breaks faster-whisper 1.2.1 local transcription. Install beta 16 for voice notes.

Beta 15 introduced Core 1.1.0b8 routing for already-transcribed voice notes and Telegram audio-file STT. Its source, wheels and manifest are retained as immutable history.

OpenAgent v1.1.0-beta.14

OpenAgent v1.1.0-beta.14 attachment previews

The App uses one attachment component for user and agent messages. Image and video attachments open in an expanded viewer with adjacent Expand and Download controls. Audio attachments expose inline play/pause and seeking. PDF, text and code files open in a preview; code uses the App's existing Shiki renderer. Unsupported document types remain downloadable. The same component applies in App chat surfaces that use MessageList.

All nine Python product distributions advance together to beta 14 while retaining Core beta 7. The release changes the client attachment presentation; it does not add a GlassPalace-specific override to the OpenAgent runtime. The standalone server, CLI and model configuration retain the beta 13 ImageGen capability.

The web export and TypeScript check passed. The nine wheels were built from the product workspace with unique payload ownership. Native desktop packaging and published release assets are recorded separately when qualified.

OpenAgent v1.1.0-beta.13

OpenAgent 1.1.0b13 pins Core 1.1.0b7 across the standalone server, CLI and App transport. The shared media tool now recognizes image generation advertised on a chat model and sends the provider's exact image model ID. A Claude subscription chat can invoke the tool when a separate image-capable provider is configured; the Claude subscription proxy itself does not expose an image endpoint.

The nine Python product wheels were built from commit 9093dad. In an isolated Python 3.12 environment, the exact product/Core/Tools wheel set passed dependency checking, server selfcheck and CLI tests (99 passed, one skipped). This prerelease is development-unqualified while live Friday image delivery and native installer checks are recorded separately.

OpenAgent v1.1.0-beta.12

OpenAgent v1.1.0-beta.12 publishes the server, CLI and Apple Silicon desktop App with configurable image-generation models and generated-image delivery through the existing channel attachment path. It uses Core v1.1.0-beta.6 and Tools v1.0.0-beta.3.

The nine Python wheels and desktop installers were built from commit bfbe25c24b4d6070c88275d69468541a874bfb11. A fresh Python 3.13 install passed dependency checking, server selfcheck and the CLI suite (99 passed, one skipped). The macOS App passed strict Developer ID verification, Apple notarization, stapling, Gatekeeper and packaged-artifact smoke. The DMG was separately notarized and stapled. The product manifest remains development-unqualified: Windows/Linux desktop installers and provider-backed image generation have not been qualified by this release.

OpenAgent v1.1.0-beta.11

OpenAgent v1.1.0-beta.11 adds configurable image-generation models to the server, CLI, and App, and lets agents return generated images through supported channel media delivery. It uses OpenAgent Core v1.1.0-beta.6 and OpenAgent Tools v1.0.0-beta.3.

This release publishes the Python product wheels and hash manifests from commit f370c4b34d9f15b8046b20b83d8608f888cc3639. The current signed macOS desktop installer remains v1.1.0-beta.10 while the new desktop package completes signing and notarization. The product manifest is marked development-unqualified; verify the complete wheelhouse before standalone deployment.

OpenAgent v1.1.0-beta.9 (Python artifacts)

OpenAgent v1.1.0-beta.9 is a Python artifact beta: server, CLI, bridge and product packages now resolve with Core 1.1.0b5, Sessions 1.1.0b2 and independent host-tools 1.0.0b4. The new local tool catalog and exact-run controls are available in this package set.

Source commit: 9dc0fd6. Clean nine-wheel build and product release manifests are attached. From the exact wheelhouse in a fresh environment, dependency check, server selfcheck, CLI version and 58 integration/transport/packaging tests with 21 subtests passed. Replio installed-wheel E2E also passed (2 tests). An installed CLI opened an authenticated PAKE/Iroh terminal against a temporary server, completed a two-call deterministic model exchange, and exited cleanly.

Scope: Python distributions only. The release manifest is marked development-unqualified. It does not contain signed/notarized desktop App/CLI bundles or switch updater feeds. Existing installed App/CLI bundles still use their prior host-tools lock. See docs/releases/v1.1.0-beta.9.md for the qualification boundary and remaining gates.

Manifest SHA-256: b0b379ac3e015dd7ef8a23f020b04737f126e184ac1ab20c7c114c671001a852. All 11 downloaded release assets matched the local build bytes.