antechamber 1.0.41 → 2.0.1

package/CHANGELOG.md

@@ -7,6 +7,103 @@ and this project uses [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [2.0.1] - 2026-11-11
+
+- test: remove two races the v2 release run hit
+
+## [2.0.0] - 2026-11-11
+
+### Added
+
+- **One OpenChamber extension for everything.** `extensions/antechamber` replaces OmO Graph, OmO Work and OmO
+  Compatibility: the Graph rail panel and page, the Work Status section and the OmO tool-card headers come in one
+  package, behind one approval. Install it from `https://github.com/eliottness/antechamber` (the repository root is the
+  extension; `#extension/antechamber` also works), then
+  set Settings → OpenCode CLI to its `bin/opencode-antechamber` (the Graph panel's settings show the path). On its
+  first start the launcher installs, with Bun, the antechamber release the extension's version names and the OmO
+  that release pins, into `~/.antechamber/runtime/<version>`; the extension's service installs it ahead of time when a
+  panel opens. Updating the extension in Settings → Extensions updates antechamber and OmO together, and OpenChamber's
+  own Update action points there. `ANTECHAMBER_RUNTIME_DIR` and `ANTECHAMBER_RUNTIME_SPEC` move or replace the runtime.
+- Warn when the event loop is blocked for more than 250 ms or an HTTP request takes more than 1000 ms.
+  Configure these thresholds with `ANTECHAMBER_EVENT_LOOP_LAG_MS` and `ANTECHAMBER_SLOW_REQUEST_MS`.
+  Request warnings use route patterns and omit query strings and path identifiers.
+
+### Removed
+
+- **Breaking:** OpenChamber 1.x frontend support. OpenChamber **2.3.2+** is now required.
+  The following legacy routes now use the ordinary 404 response; `/global/health`,
+  the 2.x event streams, retained uncertain compatibility probes and the CLI
+  `--version` / `upgrade` commands remain available:
+  - `GET /session`
+  - `POST /session`
+  - `GET /session/status`
+  - `GET /project/current`
+  - `GET /project`
+  - `GET /config`
+  - `GET /global/config`
+  - `GET /provider`
+  - `GET /config/providers`
+  - `GET /experimental/session`
+  - `GET /question`
+  - `GET /permission`
+  - `GET /lsp`
+  - `GET /experimental/tool/ids`
+  - `GET /provider/auth`
+  - `GET /command`
+  - `GET /path`
+  - `GET /vcs`
+  - `GET /agent`
+  - `GET /find/file`
+  - `PATCH /config`
+  - `POST /experimental/control-plane/move-session`
+  - `GET /global/event`
+  - `GET /session/{sessionID}`
+  - `PATCH /session/{sessionID}`
+  - `DELETE /session/{sessionID}`
+  - `GET /session/{sessionID}/message`
+  - `GET /session/{sessionID}/todo`
+  - `POST /session/{sessionID}/prompt_async`
+  - `POST /session/{sessionID}/message`
+  - `POST /session/{sessionID}/abort`
+  - `POST /session/{sessionID}/fork`
+  - `POST /session/{sessionID}/revert`
+  - `POST /session/{sessionID}/unrevert`
+  - `POST /session/{sessionID}/summarize`
+  - `POST /session/{sessionID}/shell`
+  - `POST /session/{sessionID}/command`
+  - `POST /session/{sessionID}/share`
+  - `DELETE /session/{sessionID}/share`
+  - `POST /question/{requestID}/reply`
+  - `POST /question/{requestID}/reject`
+  - `POST /permission/{requestID}/reply`
+  - `PUT /auth/{providerID}`
+  - `POST /provider/{providerID}/oauth/authorize`
+  - `POST /provider/{providerID}/oauth/callback`
+  - `POST /global/upgrade`
+  - `GET /event`
+
+### Changed
+
+- **Breaking:** the `omo-graph`, `omo-work` and `omo-compat` extensions and their `extension/omo-*` branches are
+  retired. Remove them in Settings → Extensions and install the `antechamber` extension; its Graph paths and Work
+  settings start empty because OpenChamber keys stored data by extension id.
+- **Breaking:** the antechamber npm package depends on `omo-ai` at an exact version, and antechamber runs that OmO by
+  default. `ANTECHAMBER_PI_BINARY` still selects another agent, and `omo` on PATH is used only when the pinned one is
+  not installed.
+- When the extension launches antechamber (`ANTECHAMBER_MANAGED=openchamber-extension`), `antechamber upgrade` and
+  `ANTECHAMBER_AUTO_UPDATE` refuse to touch npm and say to update the extension instead, and `antechamber doctor`
+  gives the same advice.
+- Move the session registry to SQLite with WAL and row-level writes. Existing `sessions.json` registries migrate
+  automatically and remain on disk as timestamped backups. After a rollback to 1.x and back, the sessions 1.x created
+  or changed in the meantime are merged in.
+- **Breaking:** antechamber now runs on Bun 1.4+ instead of Node.js. OmO already requires Bun, and under Bun the
+  server starts about 3 times faster and idles at about half the memory. `dist/cli.js` has a `bun` shebang,
+  `bin/opencode-antechamber` finds Bun on PATH, in `$BUN_INSTALL/bin` or in `~/.bun/bin`, and `antechamber doctor`
+  replaces its `node` check with a `bun` check. Launchers written by `antechamber setup --auto-update` now put
+  Bun's directory on PATH. A launcher written by an older version needs `bun` on OpenChamber's PATH; if it is not
+  there, rerun `antechamber setup --auto-update`. npm still installs and updates the package; building from source
+  still needs Node.js 22+.
+
 ## [1.0.41] - 2026-11-09
 
 ### Fixed

package/README.md

@@ -27,8 +27,7 @@ an **external OpenCode server** and sessions run on OmO.
 - Tool calls rendered as native OpenChamber tool parts (bash, write, edit,
   and so on), including subagent/task cards.
 - Approvals and questions bridged through pi's extension-UI protocol.
-- Todo list bridging from pi/OmO's todo tool to OpenChamber's task panel
-  (OpenChamber 1.x; on 2.x, the OmO Work section shows it by phase).
+- OmO's todo list, grouped by phase, in the extension's OmO Work section.
 - Fork, revert, and unrevert backed by the agent's session tree, not a
   filesystem snapshot. Reverting changes conversation context only; it never
   touches files on disk.
@@ -38,10 +37,10 @@ an **external OpenCode server** and sessions run on OmO.
   ownership tracking for detached task-host processes it spawned.
 - Idle reaping and a live-process cap (`ANTECHAMBER_MAX_LIVE`) so long-running
   deployments don't accumulate agent processes.
-- Optional [OpenChamber extensions](#openchamber-extensions): **OmO Graph**
-  draws the OmO sub-agents behind the open session as a live, clickable graph,
-  and **OmO Work** (OpenChamber 2.x) shows the session's todo phases,
-  monitors, eval cells and other background work in the Work Status panel.
+- [One OpenChamber extension](#the-openchamber-extension) that installs and
+  updates antechamber and OmO for you, draws the OmO sub-agents behind the open
+  session as a live graph (**OmO Graph**), shows the todo phases and goal timer
+  in the Work Status panel (**OmO Work**), and titles OmO's tool cards.
 
 ## Supported backends
 
@@ -50,15 +49,17 @@ an **external OpenCode server** and sessions run on OmO.
 | [OmO](https://github.com/code-yeongyu/oh-my-openagent) (`omo`, package `omo-ai`) | **default and supported**: titles, steering, subagent cards, structured questions, and private task-host teardown are built and tested against it |
 | [pi](https://github.com/badlogic/pi-mono) (`@earendil-works/pi-coding-agent`) | opt-in, best effort: set `ANTECHAMBER_PI_BINARY=pi`; OmO-specific features are unavailable |
 
-antechamber spawns `omo` from `PATH` unless `ANTECHAMBER_PI_BINARY` names
-another executable (see [docs/configuration.md](docs/configuration.md)).
+Each antechamber release depends on one exact `omo-ai` version and runs that
+OmO, so the pair you get is the pair that was tested together.
+`ANTECHAMBER_PI_BINARY` selects another executable; `omo` on `PATH` is the
+fallback when the pinned one is not installed (see
+[docs/configuration.md](docs/configuration.md)).
 
 ## Compatibility
 
 | OpenChamber | API | Status |
 |---|---|---|
-| >= 2.0.4 | v2 (`@opencode-ai/sdk/v2`) | primary target; antechamber advertises `opencode v2.1.0` on `--version` (OpenChamber 2.5.2 requires 2.1.0) |
-| 1.24.x | v1 | supported |
+| >= 2.3.2 | v2 (`/api/*`) | supported; antechamber advertises `opencode v2.999.0` on `--version` |
 | other versions | - | not tested |
 
 OpenChamber changes which OpenCode API calls it makes between releases. If a
@@ -69,7 +70,25 @@ and event-stream inventory.
 
 ## Quick start
 
-Needs Node.js 22+ and OmO's `omo` command on PATH (`bun add -g omo-ai`).
+Needs [Bun](https://bun.sh) 1.4+ on the machine OpenChamber runs on.
+
+### As an OpenChamber extension (recommended)
+
+1. In OpenChamber 2.3.2 or newer, open **Settings → Extensions → Add → URL** and
+   enter `https://github.com/eliottness/antechamber`.
+2. Approve **sessions** and the **local service** (it runs `bun`).
+3. Open the **OmO** rail panel's settings: the **Runtime** block shows the
+   install and the launcher path,
+   `<OpenChamber data dir>/extensions/antechamber/extensions/antechamber/bin/opencode-antechamber`
+   for the repository URL.
+4. Paste that path into **Settings → OpenCode CLI**.
+
+The launcher installs the antechamber release named by the extension's version,
+and the OmO it pins, into `~/.antechamber/runtime/<version>` the first time it
+starts. Updating the extension in Settings → Extensions is how antechamber and
+OmO are updated. Details: [extensions/antechamber/README.md](extensions/antechamber/README.md).
+
+### From npm
 
 ```bash
 npm i -g antechamber
@@ -78,9 +97,10 @@ antechamber doctor
 antechamber setup --auto-update
 ```
 
-`setup` updates OpenChamber's `opencodeBinary`, preserves all other settings,
-and backs up an existing settings file before changing it. Restart OpenChamber
-after setup. Preview changes with `antechamber setup --dry-run`.
+The npm package brings its pinned OmO along. `setup` updates OpenChamber's
+`opencodeBinary`, preserves all other settings, and backs up an existing
+settings file before changing it. Restart OpenChamber after setup. Preview
+changes with `antechamber setup --dry-run`.
 
 `--auto-update` keeps antechamber current without any action from you. It
 writes a small launcher, `~/.config/antechamber/opencode-antechamber`, and points
@@ -92,13 +112,10 @@ skips the check. It needs a global npm or bun install, so it is refused for
 source checkouts and `npx`. Drop the flag (plain `antechamber setup`) to point
 OpenChamber back at the `antechamber` bin and stop auto-updates.
 
-Optionally, add the bundled [OpenChamber extensions](#openchamber-extensions):
-`setup` ends by printing their folders (under
-`$(npm root -g)/antechamber/extensions/`). In OpenChamber, open
-**Settings → Extensions → Add → Folder**, paste a path, and approve the
-permissions it asks for. On OpenChamber 2.x, add OmO Work to see monitors,
-eval cells and the todo list in the Work Status panel. The folders are updated
-in place by `npm update -g`.
+`setup` ends by printing the bundled extension's folder (under
+`$(npm root -g)/antechamber/extensions/antechamber`); add it with
+**Settings → Extensions → Add → Folder** for the Graph, Work and tool headers.
+OpenChamber can keep using the npm-installed `antechamber` as its OpenCode CLI.
 
 For an isolated OpenChamber instance, leaving your main settings untouched:
 
@@ -146,9 +163,9 @@ antechamber serve --hostname 127.0.0.1 --port 4096
 |---|---|
 | `antechamber serve` | OpenCode-compatible server; `--hostname`/`--host`, `--port`, `--directory`. Bare `antechamber` also starts the server. |
 | `antechamber setup` | Configure OpenChamber; `--settings <file>`, `--profile <dir>`, `--binary <path>`, `--dry-run`, `--systemd [unit]`, `--pi-binary <path>`, `--restart`, `--auto-update`. |
-| `antechamber doctor` | Read-only Node, backend, agent/state directories, teardown, OpenChamber and auth checks, plus the installed, latest released and running adapter versions (a running server older than the install needs an OpenChamber restart); `--json`, `--settings <file>`, `--profile <dir>`. Exits 1 on any FAIL; warnings do not fail. |
-| `antechamber upgrade` | Install the latest release over a global npm or bun install, with the package manager that owns it. Refused for source checkouts and `npx`. |
-| `antechamber version` | Package version plus OpenCode API contract version. `--version`/`-v` deliberately print exactly `opencode v2.1.0` for OpenChamber. |
+| `antechamber doctor` | Read-only Bun, backend, agent/state directories, teardown, OpenChamber and auth checks, plus the installed, latest released and running adapter versions (a running server older than the install needs an OpenChamber restart); `--json`, `--settings <file>`, `--profile <dir>`. Exits 1 on any FAIL; warnings do not fail. |
+| `antechamber upgrade` | Install the latest release over a global npm or bun install, with the package manager that owns it. Refused for source checkouts, `npx`, and when the extension's launcher manages antechamber (see Upgrade, uninstall and rollback below). |
+| `antechamber version` | Package version plus OpenCode API contract version. `--version`/`-v` deliberately print exactly `opencode v2.999.0` for OpenChamber. |
 | `antechamber help` | Usage and options; also `--help`/`-h`. |
 
 ## Upgrade, uninstall and rollback
@@ -165,13 +182,11 @@ Restart OpenChamber, or `systemctl --user restart openchamber.service` for a
 managed service. Run `antechamber doctor` again. If the executable moved,
 rerun `antechamber setup`.
 
-OpenChamber 2.3.2 and later can show an "OpenCode update" notice because antechamber
-reports OpenCode API 2.1.0, the minimum OpenChamber 2.5.2 accepts. The notice names
-an OpenCode version, but its **Update** button runs `<opencodeBinary> upgrade`,
-which upgrades antechamber itself (a no-op when it is already current). Click
-**Reload OpenCode** afterwards to restart onto the new version. OpenChamber
-1.x shows no notice; its `POST /global/upgrade` call upgrades antechamber the
-same way.
+OpenChamber can show an "OpenCode update" notice. Its **Update** button runs
+`<opencodeBinary> upgrade`: for an npm install that upgrades antechamber itself
+(a no-op when it is already current); for the extension's launcher it only says
+to update the extension in Settings → Extensions. Click **Reload OpenCode**
+afterwards to restart onto the new version.
 
 To roll back wiring, copy the backup printed by setup over the settings file:
 
@@ -196,119 +211,53 @@ git clone https://github.com/eliottness/antechamber.git
 cd antechamber
 npm ci
 npm run build
-node dist/cli.js doctor
-node dist/cli.js setup --binary "$PWD/bin/opencode-antechamber"
+bun dist/cli.js doctor
+bun dist/cli.js setup --binary "$PWD/bin/opencode-antechamber"
 # isolated alternative:
-node dist/cli.js setup --profile ~/.config/antechamber-openchamber \
+bun dist/cli.js setup --profile ~/.config/antechamber-openchamber \
   --binary "$PWD/bin/opencode-antechamber"
 ```
 
-The source launcher requires the built `dist/cli.js`. Pull updates, run
+Building needs Node.js 22+ for the development tooling; the built CLI runs on
+Bun. The source launcher requires the built `dist/cli.js` and finds Bun on PATH,
+in `$BUN_INSTALL/bin` or in `~/.bun/bin`. Pull updates, run
 `npm ci && npm run build`, and restart OpenChamber.
 
-`npm run build` also builds the OmO Graph and OmO Work extensions; `setup`
-prints their folders (`$PWD/extensions/omo-dag`, `$PWD/extensions/omo-work`) to
-add in **Settings → Extensions → Add → Folder**.
-
-## OpenChamber extensions
-
-antechamber ships three optional OpenChamber extensions, in the npm package and
-attached to every GitHub release. None is required to run sessions.
-
-| Extension | Adds | OpenChamber | Asks for |
-|---|---|---|---|
-| [OmO Graph](#omo-graph) (`extensions/omo-dag`) | a rail panel drawing the session's OmO sub-agents as a live graph | 1.22 or newer | sessions, local service |
-| [OmO Work](#omo-work) (`extensions/omo-work`) | a Work Status section with the session's todo phases, monitors, eval cells, background sessions and goal timer | 2.3.2 or newer | local service |
-| [OmO Compatibility](#omo-compatibility) (`extensions/omo-compat`) | headers for OmO tool cards, such as `JS Eval` on eval cells | 1.24 or newer | nothing |
-
-All three run on OpenChamber web and desktop; VS Code and mobile load no
-extensions.
-
-### Installing an extension
-
-In OpenChamber, open **Settings → Extensions → Add** and pick the source that
-fits where OpenChamber runs:
-
-| OpenChamber runs | Add | OmO Graph | OmO Work | OmO Compatibility |
-|---|---|---|---|---|
-| anywhere (recommended) | **URL** (Git) | `https://github.com/eliottness/antechamber#extension/omo-graph` | `…#extension/omo-work` | `…#extension/omo-compat` |
-| on the machine where antechamber is installed | **Folder** | `extensions/omo-dag` | `extensions/omo-work` | `extensions/omo-compat` |
-| anywhere, offline | **ZIP file** | `antechamber-omo-graph.zip` | `antechamber-omo-work.zip` | `antechamber-omo-compat.zip` |
-
-- **URL**: a Git install from the branch every release publishes. OpenChamber
-  offers to update it after each release. Keep the `#extension/...` part: 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".
-- **Folder**: the paths `antechamber setup` prints, under
-  `$(npm root -g)/antechamber/` for npm installs or the checkout after
-  `npm run build`.
-- **ZIP file**: attached to every GitHub release, or built with
-  `npm run build && npm run pack:extension -- antechamber-omo-graph.zip` (OmO
-  Graph) or `npm run pack:work-extension -- antechamber-omo-work.zip` (OmO
-  Work). OpenChamber never updates ZIP installs.
-
-Then approve the permissions it asks for. See
-[Upgrading the OpenChamber extensions](#upgrading-the-openchamber-extensions)
-for how each source moves to a new release.
-
-### OmO Graph
-
-With the default OmO backend, OmO Graph adds a rail panel showing the open
-session's orchestrator and every sub-agent OmO launched, grouped in waves:
-
-- each card shows the sub-agent's live state, duration, agent and model;
-- hovering a card highlights its input and output edges;
-- clicking a card opens that sub-agent's session.
-
-Its local service reads OmO's task store and antechamber's session registry
-read-only. Details: [extensions/omo-dag/README.md](extensions/omo-dag/README.md).
-
-### OmO Work
-
-OmO Work adds an **OmO Work** section to OpenChamber 2.x's Work Status panel,
-for the background work of the open session:
-
-- the OmO todo list grouped by phase, with progress per phase;
-- terminal monitors, with their command, filter and latest matched lines (on
-  2.x, monitors appear here instead of as subagent sessions);
-- detached eval cells, with their output and a **Stop** button;
-- background terminal sessions that are still running;
-- the goal continuation timer, what it waits on, and a **Fire now** button.
-
-Its local service talks to the running antechamber through the
-`/antechamber/work-status` routes, authenticated by a token antechamber writes
-into its private run record, so it never needs the server password. It needs
-antechamber running on the same machine as OpenChamber. Details:
-[extensions/omo-work/README.md](extensions/omo-work/README.md).
-
-### OmO Compatibility
-
-OmO Compatibility is a manifest with no code. 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. It
-needs no build. 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.
+`npm run build` also builds the extension; `setup` prints its folder
+(`$PWD/extensions/antechamber`) to add in **Settings → Extensions → Add →
+Folder**. To run a checkout through the extension's launcher instead, `npm pack`
+it and set `ANTECHAMBER_RUNTIME_SPEC` to the tarball in OpenChamber's
+environment.
+
+## The OpenChamber extension
+
+`extensions/antechamber` is one OpenChamber 2.3.2+ extension (web and desktop;
+VS Code and mobile load no extensions). It replaces the OmO Graph, OmO Work and
+OmO Compatibility extensions of antechamber 1.x: remove those, then add this
+one.
+
+| Part | What it does |
+|---|---|
+| Runtime | `bin/opencode-antechamber`, OpenChamber's OpenCode CLI: installs and runs the pinned antechamber and OmO with Bun |
+| OmO Graph | a rail panel (and page) drawing the open session's OmO sub-agents as a live, clickable graph |
+| OmO Work | a Work Status section with the session's todo phases, goal timer and other wake sources |
+| Tool headers | eval cells read `JS Eval`/`Python Eval` and their summary; sub-agent cards read their agent and description |
+
+Add it from **Settings → Extensions → Add**:
+
+| Source | Add | Updates |
+|---|---|---|
+| **URL** (Git, recommended) | `https://github.com/eliottness/antechamber` (the repository root is the extension), or `…#extension/antechamber` for a clone of just the extension | OpenChamber offers **Update** after each release |
+| **Folder** | `extensions/antechamber` of an npm install or a built checkout | changes with the installation |
+| **ZIP** | `antechamber-openchamber.zip` from a GitHub release, or `npm run build && npm run pack:extension -- out.zip` | never; reinstall the new archive |
+
+Both URLs install the same extension: the root `package.json` carries its
+manifest, pointing into `extensions/antechamber/`, whose built files are
+committed. It asks
+for **sessions** and a **local service** (`bun`). Details, data paths and the
+design: [extensions/antechamber/README.md](extensions/antechamber/README.md),
+[docs/GRAPH.md](extensions/antechamber/docs/GRAPH.md),
+[docs/WORK.md](extensions/antechamber/docs/WORK.md).
 
 ## Configuration
 
@@ -401,9 +350,7 @@ provenance and creates the GitHub release from the CHANGELOG. See
 - [docs/backends/omo.md](docs/backends/omo.md) - OmO backend details (agent name, task hosts, transcripts)
 - [RELEASE.md](RELEASE.md) - automatic patch releases to npm and GitHub on every push to `main`
 
-- [extensions/omo-dag/README.md](extensions/omo-dag/README.md) - the OmO Graph OpenChamber extension ([design](extensions/omo-dag/docs/DESIGN.md))
-- [extensions/omo-work/README.md](extensions/omo-work/README.md) - the OmO Work status section for OpenChamber 2.x ([design](extensions/omo-work/docs/DESIGN.md))
-- [extensions/omo-compat/README.md](extensions/omo-compat/README.md) - the OmO Compatibility display rules
+- [extensions/antechamber/README.md](extensions/antechamber/README.md) - the OpenChamber extension: runtime launcher, OmO Graph ([design](extensions/antechamber/docs/GRAPH.md)), OmO Work ([design](extensions/antechamber/docs/WORK.md)) and tool headers
 
 ## Credits
 

package/bin/opencode-antechamber

@@ -3,7 +3,7 @@
 # at this file. OpenChamber runs `<binary> serve --hostname H --port P` and
 # `<binary> --version`, and OpenChamber 2.x's Update action runs `<binary> upgrade`;
 # anything else is rejected.
-# Requires a build (`npm run build`) so that dist/cli.js exists.
+# Requires a build (`npm run build`) so that dist/cli.js exists, and Bun to run it.
 set -eu
 SCRIPT_PATH=$0
 while [ -h "$SCRIPT_PATH" ]; do
@@ -20,10 +20,20 @@ if [ ! -f "$CLI" ]; then
   echo "opencode-antechamber: $CLI not found; run 'npm run build' first" >&2
   exit 1
 fi
+# antechamber runs on Bun. GUI apps and services often have a PATH without
+# Bun's install directory, so also look where the Bun installer puts it.
+BUN=$(command -v bun || true)
+for CANDIDATE in "${BUN_INSTALL:-${HOME:-}/.bun}/bin/bun" "${HOME:-}/.bun/bin/bun"; do
+  if [ -z "$BUN" ] && [ -x "$CANDIDATE" ]; then BUN=$CANDIDATE; fi
+done
+if [ -z "$BUN" ]; then
+  echo "opencode-antechamber: bun not found on PATH or in ~/.bun/bin; install it from https://bun.sh" >&2
+  exit 1
+fi
 case "${1:-}" in
-  serve) shift; exec node "$CLI" serve "$@" ;;
-  --version|-v) exec node "$CLI" --version ;;
-  upgrade) exec node "$CLI" upgrade ;;
+  serve) shift; exec "$BUN" "$CLI" serve "$@" ;;
+  --version|-v) exec "$BUN" "$CLI" --version ;;
+  upgrade) exec "$BUN" "$CLI" upgrade ;;
 esac
 echo "opencode-antechamber: unsupported command '${1:-}' (only 'serve', '--version' and 'upgrade' are implemented)" >&2
 exit 1

package/dist/cli.d.ts

@@ -1,2 +1,2 @@
-#!/usr/bin/env node
+#!/usr/bin/env bun
 export {};

package/dist/cli.js

@@ -1,4 +1,4 @@
-#!/usr/bin/env node
+#!/usr/bin/env bun
 /** CLI parsing and dispatch. Server code is loaded only for serve/default mode. */
 import { parseArgs } from "node:util";
 import { ADAPTER_VERSION, OPENCODE_API_VERSION } from "./version.js";

package/dist/commands/context.d.ts

@@ -7,7 +7,10 @@ export interface CommandContext {
     readonly exec: (binary: string, args: readonly string[]) => string;
     readonly now: () => Date;
     readonly platform: NodeJS.Platform;
-    readonly nodeVersion: string;
+    /** Bun's version, or undefined when this process is not running on Bun. */
+    readonly bunVersion: string | undefined;
+    /** The running Bun executable, or undefined when this process is not running on Bun. */
+    readonly bunBinary: string | undefined;
     readonly output: (line: string) => void;
     readonly cliPath: string;
     readonly launcherPath: string;
@@ -24,6 +27,6 @@ export declare function readSettings(path: string, ctx: CommandContext): Record<
 export declare function shellQuote(value: string): string;
 /** OpenChamber launcher written by `setup --auto-update`, kept beside the session registry. */
 export declare function autoUpdateLauncherPath(ctx: CommandContext): string;
-export declare function autoUpdateLauncherText(binary: string): string;
+export declare function autoUpdateLauncherText(binary: string, bunBinary?: string): string;
 export declare function autoUpdateLauncherTarget(text: string): string | undefined;
 export declare function isPackageBinary(binary: string, ctx: CommandContext): boolean;

package/dist/commands/context.js

@@ -1,7 +1,7 @@
 import { spawnSync } from "node:child_process";
 import * as fs from "node:fs";
 import { homedir } from "node:os";
-import { delimiter, isAbsolute, join, resolve } from "node:path";
+import { delimiter, dirname, isAbsolute, join, resolve } from "node:path";
 import { fileURLToPath } from "node:url";
 import { defaultStateDir, envSetting } from "../config.js";
 export function createContext(overrides = {}) {
@@ -29,7 +29,8 @@ export function createContext(overrides = {}) {
         },
         now: () => new Date(),
         platform: process.platform,
-        nodeVersion: process.versions.node,
+        bunVersion: process.versions.bun,
+        bunBinary: process.versions.bun === undefined ? undefined : process.execPath,
         output: console.log,
         cliPath: packageCliPath,
         launcherPath: fileURLToPath(new URL("../../bin/opencode-antechamber", import.meta.url)),
@@ -85,13 +86,16 @@ export function shellQuote(value) {
 export function autoUpdateLauncherPath(ctx) {
     return resolve(ctx.cwd, envSetting("STATE_DIR", ctx.env) ?? defaultStateDir(ctx.home, ctx.fs.existsSync), "opencode-antechamber");
 }
-export function autoUpdateLauncherText(binary) {
+export function autoUpdateLauncherText(binary, bunBinary) {
+    const quote = (value) => `'${value.replaceAll("'", "'\\''")}'`;
     return [
         "#!/bin/sh",
         "# Written by `antechamber setup --auto-update`; rerun `antechamber setup` without it to stop auto-updates.",
         "ANTECHAMBER_AUTO_UPDATE=1",
         "export ANTECHAMBER_AUTO_UPDATE",
-        `exec '${binary.replaceAll("'", "'\\''")}' "$@"`,
+        // The CLI's `env bun` shebang must find Bun even when OpenChamber's PATH lacks its directory.
+        ...(bunBinary === undefined ? [] : [`PATH=${quote(dirname(bunBinary))}:"$PATH"`, "export PATH"]),
+        `exec ${quote(binary)} "$@"`,
         "",
     ].join("\n");
 }

package/dist/commands/doctor.js

@@ -1,7 +1,7 @@
 import { dirname, resolve } from "node:path";
 import { piAgentDir } from "../agent-dir.js";
 import { detectAgentName } from "../agent-name.js";
-import { agentBinary, defaultStateDir, envSetting, isPlainPi } from "../config.js";
+import { agentBinary, defaultStateDir, envSetting, isPlainPi, managedByExtension } from "../config.js";
 import { findPidfdPython } from "../pidfd.js";
 import { readRunningServers } from "../running-servers.js";
 import { isNewerVersion } from "../self-update.js";
@@ -23,7 +23,8 @@ export function doctor(options = {}, ctx = createContext(), latestVersion) {
     const add = (name, status, message) => {
         checks.push({ name, status, message });
     };
-    add("node", Number(ctx.nodeVersion.split(".")[0]) >= 22 ? "PASS" : "FAIL", `Node ${ctx.nodeVersion}; requires >=22`);
+    const [bunMajor = 0, bunMinor = 0] = (ctx.bunVersion ?? "").split(".").map(Number);
+    add("bun", bunMajor > 1 || (bunMajor === 1 && bunMinor >= 4) ? "PASS" : "FAIL", ctx.bunVersion === undefined ? "not running on Bun; requires Bun >=1.4" : `Bun ${ctx.bunVersion}; requires >=1.4`);
     const backend = agentBinary(ctx.env);
     const binary = resolveBinary(backend, ctx);
     if (binary === undefined)
@@ -59,7 +60,7 @@ export function doctor(options = {}, ctx = createContext(), latestVersion) {
     if (latestVersion instanceof Error)
         add("version", "INFO", `${ADAPTER_VERSION}; latest unknown (${latestVersion.message})`);
     else if (latest !== undefined && isNewerVersion(latest, ADAPTER_VERSION))
-        add("version", "WARN", `${ADAPTER_VERSION} installed; ${latest} is released: run antechamber upgrade`);
+        add("version", "WARN", `${ADAPTER_VERSION} installed; ${latest} is released: ${managedByExtension(ctx.env) ? "update the antechamber extension in OpenChamber" : "run antechamber upgrade"}`);
     else
         add("version", "PASS", ADAPTER_VERSION);
     // A released fix is live only once OpenChamber relaunches the adapter.

package/dist/commands/setup.js

@@ -12,23 +12,12 @@ function writeAtomically(path, content, ctx) {
     ctx.fs.writeFileSync(temporary, content, { mode: 0o600, flag: "wx" });
     ctx.fs.renameSync(temporary, path);
 }
-/** The bundled OmO Graph extension folder, when this installation has its built files. */
-function omoGraphExtensionDir(ctx) {
-    const dir = resolve(dirname(ctx.cliPath), "..", "extensions", "omo-dag");
-    const built = ["package.json", "panel/main.js", "service/main.js"].every((file) => ctx.fs.existsSync(join(dir, file)));
+/** The bundled antechamber OpenChamber extension folder, when this installation has its built files. */
+function antechamberExtensionDir(ctx) {
+    const dir = resolve(dirname(ctx.cliPath), "..", "extensions", "antechamber");
+    const built = ["package.json", "panel/main.js", "status/main.js", "service/main.js", "runtime/launcher.js"].every((file) => ctx.fs.existsSync(join(dir, file)));
     return built ? dir : undefined;
 }
-/** The bundled OmO Work status-section extension folder, when this installation has its built files. */
-function omoWorkExtensionDir(ctx) {
-    const dir = resolve(dirname(ctx.cliPath), "..", "extensions", "omo-work");
-    const built = ["package.json", "status/main.js", "service/main.js"].every((file) => ctx.fs.existsSync(join(dir, file)));
-    return built ? dir : undefined;
-}
-/** The bundled OmO Compatibility extension folder; it is a manifest only, so it needs no build. */
-function omoCompatExtensionDir(ctx) {
-    const dir = resolve(dirname(ctx.cliPath), "..", "extensions", "omo-compat");
-    return ctx.fs.existsSync(join(dir, "package.json")) ? dir : undefined;
-}
 /** Plan all inputs before applying changes; dependencies are injected for hermetic tests. */
 export function setup(options, ctx = createContext()) {
     const lines = [];
@@ -49,8 +38,8 @@ export function setup(options, ctx = createContext()) {
             : ctx.cliPath;
     if (binary === undefined)
         throw new Error(`Cannot resolve executable --binary ${options.binary}`);
-    if (binary === ctx.cliPath && !ctx.fs.readFileSync(binary, "utf8").startsWith("#!/usr/bin/env node\n")) {
-        throw new Error(`Package CLI ${binary} is missing its node shebang; run npm run build`);
+    if (binary === ctx.cliPath && !ctx.fs.readFileSync(binary, "utf8").startsWith("#!/usr/bin/env bun\n")) {
+        throw new Error(`Package CLI ${binary} is missing its bun shebang; run npm run build`);
     }
     let launcher;
     let launcherText;
@@ -63,7 +52,7 @@ export function setup(options, ctx = createContext()) {
             realpath: (path) => ctx.fs.realpathSync(path),
         }, () => ctx.exec(npmBinaryFor(), ["root", "-g"]));
         launcher = autoUpdateLauncherPath(ctx);
-        launcherText = autoUpdateLauncherText(binary);
+        launcherText = autoUpdateLauncherText(binary, ctx.bunBinary);
         if (ctx.fs.existsSync(launcher))
             oldLauncher = ctx.fs.readFileSync(launcher, "utf8");
     }
@@ -181,17 +170,9 @@ export function setup(options, ctx = createContext()) {
     if (options.profile !== undefined && options.settings === undefined) {
         report(`OPENCHAMBER_DATA_DIR=${shellQuote(resolve(ctx.cwd, options.profile))} openchamber serve`);
     }
-    const extension = omoGraphExtensionDir(ctx);
+    const extension = antechamberExtensionDir(ctx);
     if (extension !== undefined) {
-        report(`Optional OmO Graph extension: in OpenChamber, Settings \u2192 Extensions \u2192 Add \u2192 Folder: ${extension}`);
-    }
-    const work = omoWorkExtensionDir(ctx);
-    if (work !== undefined) {
-        report(`Optional OmO Work section (todo phases, monitors, eval cells; OpenChamber 2.x): Settings \u2192 Extensions \u2192 Add \u2192 Folder: ${work}`);
-    }
-    const compat = omoCompatExtensionDir(ctx);
-    if (compat !== undefined) {
-        report(`Optional OmO Compatibility extension (eval card headers): Settings \u2192 Extensions \u2192 Add \u2192 Folder: ${compat}`);
+        report(`Optional antechamber extension (OmO Graph, OmO Work, OmO tool headers; OpenChamber 2.3.2+): Settings \u2192 Extensions \u2192 Add \u2192 Folder: ${extension}`);
     }
     return lines;
 }

package/dist/config.d.ts

@@ -12,7 +12,11 @@ export declare function envSetting(name: string, env?: NodeJS.ProcessEnv): strin
  * mappings survive the upgrade.
  */
 export declare function defaultStateDir(home?: string, exists?: typeof existsSync): string;
-/** Agent executable spawned per session: OmO by default, plain pi when configured. */
-export declare function agentBinary(env?: NodeJS.ProcessEnv): string;
+/** The OmO that antechamber's package.json pins, when it is installed beside antechamber. */
+export declare function bundledOmo(): string | undefined;
+/** Agent executable spawned per session: the pinned OmO by default, else `omo` on PATH, plain pi when configured. */
+export declare function agentBinary(env?: NodeJS.ProcessEnv, bundled?: () => string | undefined): string;
+/** Set by the OpenChamber extension's launcher: the extension, not npm, installs and updates antechamber. */
+export declare function managedByExtension(env?: NodeJS.ProcessEnv): boolean;
 /** True when the configured backend is upstream pi rather than OmO. */
 export declare function isPlainPi(env?: NodeJS.ProcessEnv): boolean;