antechamber 1.0.2 → 1.0.3

package/CHANGELOG.md

@@ -7,6 +7,18 @@ and this project uses [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [1.0.3] - 2026-10-20
+
+### Added
+
+- The OpenChamber extensions install by Git URL, and OpenChamber offers each release under
+  **Update** in Settings → Extensions: every release commits them to the `extension/omo-graph`,
+  `extension/omo-work` and `extension/omo-compat` branches, so add
+  `https://github.com/eliottness/antechamber#extension/omo-graph` (or `#extension/omo-work`,
+  `#extension/omo-compat`). The bare repository URL keeps failing with OpenChamber's "panel.id must
+  be kebab-case" toast, because it points at antechamber itself. ZIP installs still work but are
+  never updated.
+
 ## [1.0.2] - 2026-10-20
 
 ### Fixed

package/README.md

@@ -228,13 +228,14 @@ source fits where OpenChamber runs:
 | OpenChamber runs | Add | Value |
 |---|---|---|
 | on the machine where antechamber is installed | **Folder** | the path `antechamber setup` prints: `$(npm root -g)/antechamber/extensions/omo-dag` for npm installs, `<checkout>/extensions/omo-dag` after `npm run build` from source |
-| anywhere (remote host, browser-only access) | **URL** | `https://github.com/eliottness/antechamber/releases/latest/download/antechamber-omo-graph.zip` (attached to every GitHub release) |
-| anywhere, offline | **ZIP file** | that same `antechamber-omo-graph.zip`, downloaded, or built with `npm run build && npm run pack:extension -- antechamber-omo-graph.zip` |
+| anywhere (remote host, browser-only access) | **URL** | `https://github.com/eliottness/antechamber#extension/omo-graph`, a Git install that OpenChamber offers to update after each release |
+| anywhere, offline | **ZIP file** | `antechamber-omo-graph.zip` from a GitHub release, or built with `npm run build && npm run pack:extension -- antechamber-omo-graph.zip`. OpenChamber never updates ZIP installs |
 
 Then approve its two permissions (follow sessions, run the local service) and
-open it from the rail icon. Don't install it from the repository's Git URL:
-OpenChamber clones the repository root, which is antechamber itself, not the
-extension, and refuses it as an invalid manifest. Details:
+open it from the rail icon. Keep the `#extension/omo-graph` part of the URL:
+the bare repository URL makes OpenChamber clone antechamber itself, whose
+`package.json` is not an extension, and OpenChamber words that rejection as
+"panel.id must be kebab-case". Details:
 [extensions/omo-dag/README.md](extensions/omo-dag/README.md).
 
 ## OpenChamber extension: OmO Work
@@ -248,8 +249,8 @@ with a Fire now button. On 2.x, monitors appear here instead of as subagent
 sessions.
 
 Add it like OmO Graph: the folder `antechamber setup` prints
-(`.../extensions/omo-work`, built by `npm run build`), or
-`https://github.com/eliottness/antechamber/releases/latest/download/antechamber-omo-work.zip`.
+(`.../extensions/omo-work`, built by `npm run build`), or the URL
+`https://github.com/eliottness/antechamber#extension/omo-work`.
 Approve its local service. It needs an antechamber version that writes a
 work-status token into its run record (this release or newer) and an
 OpenChamber restart after upgrading. Details:
@@ -262,11 +263,31 @@ or newer. It tells OpenChamber how to display OmO tool calls that antechamber
 maps onto OpenChamber's cards; today it heads eval cells with `JS Eval` or
 `Python Eval` and the cell's summary. Add it the same way as OmO Graph: the
 folder `antechamber setup` prints (`.../extensions/omo-compat`, no build
-needed), or the release archive
-`https://github.com/eliottness/antechamber/releases/latest/download/antechamber-omo-compat.zip`.
+needed), or the URL
+`https://github.com/eliottness/antechamber#extension/omo-compat`.
 It asks for no permissions. Details:
 [extensions/omo-compat/README.md](extensions/omo-compat/README.md).
 
+## Upgrading the OpenChamber extensions
+
+Every antechamber release ships the three extensions at its own version. How
+an installed extension moves to a new release depends on how it was added:
+
+- **Git URL** (`https://github.com/eliottness/antechamber#extension/...`):
+  Settings → Extensions shows **Update available** once a release is out
+  (OpenChamber checks at most hourly; **Check for updates** checks now).
+  **Update** replaces it in place and keeps its approvals and settings.
+- **Folder**: the folder belongs to the antechamber installation, so it
+  changes with `antechamber upgrade` (or `git pull && npm ci && npm run build`
+  in a checkout). Toggle the extension off and on to restart its service.
+- **ZIP** (file or release URL): OpenChamber never checks these. Add the new
+  archive and choose **Reinstall**, or switch to the Git URL once: remove the
+  extension, then add it by URL.
+
+Each extension is built against the antechamber of the same release, so
+upgrade antechamber too and restart OpenChamber to run it; `antechamber
+doctor` shows the running version.
+
 ## Configuration
 
 Connector settings use the `ANTECHAMBER_` prefix; the deprecated `OCPI_`

package/extensions/omo-compat/README.md

@@ -31,8 +31,11 @@ In OpenChamber, open **Settings → Extensions → Add**:
   `$(npm root -g)/antechamber/extensions/omo-compat` for an npm install, or
   `<checkout>/extensions/omo-compat` from a source checkout. It needs no build.
 - **URL**, from anywhere:
-  `https://github.com/eliottness/antechamber/releases/latest/download/antechamber-omo-compat.zip`.
-  Every GitHub release attaches this archive.
+  `https://github.com/eliottness/antechamber#extension/omo-compat`, a Git
+  install that OpenChamber offers to update after each release. Every GitHub
+  release also attaches
+  `https://github.com/eliottness/antechamber/releases/latest/download/antechamber-omo-compat.zip`,
+  which installs by URL too, but OpenChamber never updates ZIP installs.
 
 There is nothing to approve and no rail icon. Reload open chats after
 installing so their cards pick up the new header.

package/extensions/omo-compat/package.json

@@ -1,6 +1,6 @@
 {
   "name": "antechamber-omo-compat",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "OpenChamber extension: displays OmO tool calls the way OmO means them when OpenChamber runs on antechamber",
   "private": true,
   "type": "module",

package/extensions/omo-dag/README.md

@@ -58,16 +58,18 @@ fits where OpenChamber runs:
   - source checkout: `<checkout>/extensions/omo-dag`, after `npm run build`
     (which also writes `panel/main.js` and `service/main.js`).
 - **URL**, from anywhere, including a remote OpenChamber you only reach in a
-  browser:
-  `https://github.com/eliottness/antechamber/releases/latest/download/antechamber-omo-graph.zip`.
-  Every GitHub release attaches this archive. Append a version instead of
-  `latest` (`.../releases/download/vX.Y.Z/antechamber-omo-graph.zip`) to pin
-  one.
-- **ZIP file**, for offline hosts: the same archive, downloaded, or built with
+  browser: `https://github.com/eliottness/antechamber#extension/omo-graph`.
+  Every release commits the built extension to the `extension/omo-graph`
+  branch, so OpenChamber offers it under **Update** in Settings → Extensions.
+  To pin a version instead, install its release archive by URL,
+  `https://github.com/eliottness/antechamber/releases/download/vX.Y.Z/antechamber-omo-graph.zip`;
+  OpenChamber never updates ZIP installs.
+- **ZIP file**, for offline hosts: that archive, downloaded, or built with
   `npm run build && npm run pack:extension -- antechamber-omo-graph.zip`.
 
-Don't use the repository's Git URL. OpenChamber clones the repository root,
-which is antechamber itself, and rejects it as `invalid-manifest`.
+Keep the `#extension/omo-graph` part of the URL. Without it OpenChamber clones
+the repository root, which is antechamber itself, and rejects it as
+`invalid-manifest`, which its toast words as "panel.id must be kebab-case".
 
 Approve the request. The extension asks for two things:
 

package/extensions/omo-dag/package.json

@@ -1,6 +1,6 @@
 {
   "name": "antechamber-omo-graph",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "OpenChamber extension: live, interactive graph of the OmO sub-agents behind the current session",
   "private": true,
   "type": "module",

package/extensions/omo-work/README.md

@@ -31,9 +31,12 @@ In OpenChamber, open **Settings → Extensions → Add**:
   installed: the path `antechamber setup` prints,
   `$(npm root -g)/antechamber/extensions/omo-work` for npm installs or
   `<checkout>/extensions/omo-work` after `npm run build`.
-- **URL**:
-  `https://github.com/eliottness/antechamber/releases/latest/download/antechamber-omo-work.zip`.
-- **ZIP file**: the same archive, or
+- **URL**: `https://github.com/eliottness/antechamber#extension/omo-work`, a
+  Git install that OpenChamber offers to update after each release. The
+  release archive,
+  `https://github.com/eliottness/antechamber/releases/latest/download/antechamber-omo-work.zip`,
+  also installs by URL, but OpenChamber never updates ZIP installs.
+- **ZIP file**: that archive, or
   `npm run build && npm run pack:work-extension -- antechamber-omo-work.zip`.
 
 Approve its **local service**. The section then appears in the Work Status

package/extensions/omo-work/package.json

@@ -1,6 +1,6 @@
 {
   "name": "antechamber-omo-work",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "OpenChamber 2.x Work Status section: OmO todo phases, monitors, eval cells and background work of the current session",
   "private": true,
   "type": "module",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "antechamber",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "OpenCode-compatible HTTP/SSE server that lets OpenChamber drive the pi coding agent (and OmO) over RPC",
   "type": "module",
   "license": "MIT",