antechamber 1.0.41 → 2.0.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "antechamber",
-  "version": "1.0.41",
+  "version": "2.0.1",
   "description": "OpenCode-compatible HTTP/SSE server that lets OpenChamber drive the pi coding agent (and OmO) over RPC",
   "type": "module",
   "license": "MIT",
@@ -28,22 +28,18 @@
     "dist",
     "bin/opencode-antechamber",
     "bin/opencode-pi",
-    "extensions/omo-dag/package.json",
-    "extensions/omo-dag/icon.svg",
-    "extensions/omo-dag/panel/index.html",
-    "extensions/omo-dag/panel/main.js",
-    "extensions/omo-dag/service/main.js",
-    "extensions/omo-dag/README.md",
-    "extensions/omo-dag/docs/DESIGN.md",
-    "extensions/omo-work/package.json",
-    "extensions/omo-work/status/index.html",
-    "extensions/omo-work/status/main.js",
-    "extensions/omo-work/service/main.js",
-    "extensions/omo-work/README.md",
-    "extensions/omo-work/docs/DESIGN.md",
-    "extensions/omo-compat/package.json",
-    "extensions/omo-compat/icon.svg",
-    "extensions/omo-compat/README.md",
+    "extensions/antechamber/package.json",
+    "extensions/antechamber/icon.svg",
+    "extensions/antechamber/bin/opencode-antechamber",
+    "extensions/antechamber/panel/index.html",
+    "extensions/antechamber/panel/main.js",
+    "extensions/antechamber/status/index.html",
+    "extensions/antechamber/status/main.js",
+    "extensions/antechamber/service/main.js",
+    "extensions/antechamber/runtime/launcher.js",
+    "extensions/antechamber/README.md",
+    "extensions/antechamber/docs/GRAPH.md",
+    "extensions/antechamber/docs/WORK.md",
     "README.md",
     "LICENSE",
     "CHANGELOG.md"
@@ -53,17 +49,16 @@
   },
   "scripts": {
     "build": "tsc -p tsconfig.json && node --input-type=module -e \"import { chmodSync } from 'node:fs'; chmodSync('dist/cli.js', 0o755)\" && npm run build:extension",
-    "build:extension": "tsx extensions/omo-dag/scripts/build.ts && tsx extensions/omo-work/scripts/build.ts",
-    "pack:extension": "tsx extensions/omo-dag/scripts/pack.ts",
-    "pack:work-extension": "tsx extensions/omo-work/scripts/pack.ts",
+    "build:extension": "tsx extensions/antechamber/scripts/build.ts",
+    "pack:extension": "tsx extensions/antechamber/scripts/pack.ts",
     "prepack": "npm run build",
-    "dev": "tsx src/cli.ts",
-    "typecheck": "tsc -p tsconfig.check.json && tsc -p extensions/omo-dag/tsconfig.json && tsc -p extensions/omo-work/tsconfig.json",
+    "dev": "bun src/cli.ts",
+    "typecheck": "tsc -p tsconfig.check.json && tsc -p extensions/antechamber/tsconfig.json",
     "lint": "biome lint . --error-on-warnings",
     "format": "biome format --write .",
     "format:check": "biome format .",
     "check": "npm run typecheck && npm run lint && npm run format:check && npm test",
-    "test": "tsx --test --import ./test/setup.ts test/*.test.ts extensions/*/test/*.test.ts",
+    "test": "tsx --test --import ./test/setup.ts test/*.test.ts extensions/*/test/*.test.ts extensions/*/test/*/*.test.ts",
     "probe": "tsx contrib/probe.ts",
     "smoke": "tsx contrib/smoke.ts",
     "omo-smoke": "tsx contrib/omo/omo-smoke.ts",
@@ -75,7 +70,7 @@
     "esbuild@0.28.2": true
   },
   "engines": {
-    "node": ">=22"
+    "bun": ">=1.4.0"
   },
   "publishConfig": {
     "access": "public",
@@ -83,12 +78,66 @@
   },
   "devDependencies": {
     "@biomejs/biome": "^2.5.15",
-    "@openchamber/sdk": "1.24.2",
-    "@openchamber/sdk-v2": "npm:@openchamber/sdk@2.5.0",
+    "@openchamber/sdk": "2.5.0",
     "@opencode-ai/sdk": "^1.18.31",
     "@types/node": "^22.0.0",
     "esbuild": "^0.28.2",
     "tsx": "^4.23.14",
     "typescript": "^7.0.2"
+  },
+  "dependencies": {
+    "omo-ai": "5.1.69"
+  },
+  "openchamber": {
+    "apiVersion": 1,
+    "engines": {
+      "openchamber": ">=2.3.2"
+    },
+    "contributes": {
+      "panel": {
+        "id": "antechamber",
+        "name": "OmO",
+        "icon": "extensions/antechamber/icon.svg",
+        "entry": "extensions/antechamber/panel/index.html"
+      },
+      "page": {
+        "entry": "extensions/antechamber/panel/index.html",
+        "title": "OmO Graph"
+      },
+      "statusSection": {
+        "entry": "extensions/antechamber/status/index.html",
+        "title": "OmO Work",
+        "height": 120
+      },
+      "capabilities": [
+        "sessions"
+      ],
+      "service": {
+        "entry": "extensions/antechamber/service/main.js",
+        "runtime": "host",
+        "permissions": {
+          "exec": [
+            "bun"
+          ]
+        }
+      },
+      "tools": [
+        {
+          "match": "shell",
+          "title": "{metadata.evalTitle}",
+          "subtitle": "{metadata.evalSubtitle}"
+        },
+        {
+          "match": "task",
+          "title": "{metadata.agentTitle}",
+          "subtitle": "{metadata.agentSubtitle}"
+        },
+        {
+          "match": "agent",
+          "title": "{metadata.agentTitle}",
+          "subtitle": "{metadata.agentSubtitle}"
+        }
+      ]
+    }
   }
 }

package/extensions/omo-compat/README.md

@@ -1,48 +0,0 @@
-# OmO Compatibility
-
-An OpenChamber extension that ships with antechamber. It changes how OpenChamber
-displays some OmO tool calls, using only the display rules OpenChamber lets an
-extension declare. It has no panel, page, service or permissions.
-
-What it does today:
-
-- **Subagent card headers.** A subagent an eval cell started with `agent()` is shown as a `task` card. Its header
-  reads the agent type and a short description (the call's label, the task's summary, or the prompt's first line)
-  instead of the generic "Agent Task".
-
-- **Eval cell headers.** OpenChamber 1.24 streams live output only for shell
-  cards, so antechamber shows OmO eval cells as shell cards (`bash` in OpenChamber
-  1.x, `shell` in 2.x). With this extension their header reads `JS Eval` (or
-  `Python Eval`) and the cell's summary instead of "Shell Command" and the first
-  line of code. Other shell cards keep their normal header.
-
-## Requirements
-
-- OpenChamber **1.24 or newer** (the first release with `contributes.tools`).
-- antechamber as OpenChamber's backend. Without it the rules match nothing and
-  change nothing.
-
-## Install
-
-In OpenChamber, open **Settings → Extensions → Add**:
-
-- **Folder**, when OpenChamber runs on the machine where antechamber is
-  installed. `antechamber setup` prints the path:
-  `$(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#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.
-
-For a server you reach over HTTP:
-
-```bash
-curl -sX POST "$OC/api/guests" -H 'content-type: application/json' \
-  -d '{"path":"/abs/path/to/extensions/omo-compat"}'
-```

package/extensions/omo-compat/icon.svg

@@ -1 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><title>OmO Compatibility</title><path d="M8 7 3 12l5 5"/><path d="m16 7 5 5-5 5"/><path d="M14 4l-4 16"/></svg>

package/extensions/omo-compat/package.json

@@ -1,43 +0,0 @@
-{
-  "name": "antechamber-omo-compat",
-  "version": "1.0.41",
-  "description": "OpenChamber extension: displays OmO tool calls the way OmO means them when OpenChamber runs on antechamber",
-  "private": true,
-  "type": "module",
-  "license": "MIT",
-  "openchamber": {
-    "apiVersion": 1,
-    "engines": {
-      "openchamber": ">=1.24.0"
-    },
-    "contributes": {
-      "panel": {
-        "id": "omo-compat",
-        "name": "OmO Compatibility",
-        "icon": "icon.svg"
-      },
-      "tools": [
-        {
-          "match": "bash",
-          "title": "{metadata.evalTitle}",
-          "subtitle": "{metadata.evalSubtitle}"
-        },
-        {
-          "match": "shell",
-          "title": "{metadata.evalTitle}",
-          "subtitle": "{metadata.evalSubtitle}"
-        },
-        {
-          "match": "task",
-          "title": "{metadata.agentTitle}",
-          "subtitle": "{metadata.agentSubtitle}"
-        },
-        {
-          "match": "agent",
-          "title": "{metadata.agentTitle}",
-          "subtitle": "{metadata.agentSubtitle}"
-        }
-      ]
-    }
-  }
-}

package/extensions/omo-dag/README.md

@@ -1,167 +0,0 @@
-# OmO Graph: OpenChamber extension
-
-A live, interactive graph of the OmO sub-agents behind the OpenChamber session
-you are looking at. It ships with [antechamber](../../README.md) and runs in
-OpenChamber's extension sandbox, next to the antechamber server that runs your
-sessions on OmO.
-
-- **One graph per run.** Open any session and the panel shows its
-  orchestrator plus every task OmO launched for it. Tasks are arranged in
-  waves (columns), the way [omo.dev](https://omo.dev) draws a `mass ulw`
-  workflow. Opening a sub-agent's own session shows the same run, with that
-  sub-agent outlined.
-- **Live state on every card.** Each card shows a status dot, a status line
-  such as `running · 2m 03s`, `completed · 41s` or `failed`, the agent or
-  category, the model, and the first line of the result. Running cards glow,
-  and their incoming edges carry a moving pulse. The rail icon shows a badge
-  with the number of running agents.
-- **Hover to trace** (Archify-style focus). Hovering or keyboard-focusing a
-  card highlights its **input edges** (amber) and **output edges** (accent).
-  Its transitive upstream and downstream reach stays half-lit, and everything
-  else dims. The inspector strip shows tokens, cost, tool calls, input and
-  output counts, and the result or error.
-- **Click to open.** Clicking a card opens that sub-agent's session, or the
-  orchestrator's, in the chat.
-- **Pan and zoom.** Drag the background, and scroll or pinch to zoom. `0`
-  fits the graph; the target button centres on the current or first running
-  agent.
-- Very large runs are sent within a bounded response size. When tasks are
-  omitted to fit that limit, the panel shows the omitted-node count.
-
-The panel docks in the right rail. The same page is also available full
-screen from the sidebar's Extension pages menu.
-
-On OpenChamber 2.x, the bundled [OmO Work](../omo-work/README.md) section
-complements the graph with the session's todo phases, monitors, eval cells and
-other background work.
-
-## Requirements
-
-- OpenChamber **1.22 or newer**, on web or desktop. It is verified against
-  1.24.2 and uses only the v1 extension API that 2.x hosts also accept. VS
-  Code and mobile do not load extensions.
-- antechamber running its default OmO backend, so that sub-agent sessions
-  exist in OpenChamber. A plain pi backend (`ANTECHAMBER_PI_BINARY=pi`) has no
-  sub-agents to draw.
-- The OmO task store on the same machine as the OpenChamber server
-  (`~/.omo/agent` by default).
-
-The built files run on OpenChamber's own runtime and need nothing else
-installed.
-
-## Install
-
-In OpenChamber, open **Settings → Extensions → Add** and pick the source that
-fits where OpenChamber runs:
-
-- **Folder**, when OpenChamber runs on the machine where antechamber is
-  installed. `antechamber setup` prints the path to paste:
-  - npm install: `$(npm root -g)/antechamber/extensions/omo-dag`. The
-    published package ships the built extension, and `npm update -g` updates
-    the folder in place.
-  - 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#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`.
-
-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:
-
-- **sessions**, to follow the open session and open sub-agent sessions;
-- **a local service**, to read the OmO task store.
-
-Then open it from the rail icon.
-
-For a server you reach over HTTP:
-
-```bash
-curl -sX POST "$OC/api/guests" -H 'content-type: application/json' \
-  -d '{"path":"/abs/path/to/extensions/omo-dag"}'
-curl -sX PUT "$OC/api/guests/omo-dag/capabilities" -H 'content-type: application/json' \
-  -d '{"granted":["sessions","service"]}'
-```
-
-Add your UI auth if the instance has a password. A folder install serves the
-files in place: after `npm run build`, reopen the panel. To restart a running
-service, toggle the extension off and on.
-
-## Deploying alongside antechamber
-
-1. Build antechamber in the deployment checkout (`npm ci && npm run build`).
-   That one build covers both the server and the extension.
-2. Install `<checkout>/extensions/omo-dag` once in the OpenChamber instance
-   and approve it.
-3. If deployments move between checkouts, install a stable symlink once (for
-   example `~/.local/share/antechamber/omo-dag -> <checkout>/extensions/omo-dag`)
-   so an upgrade only re-points the link.
-
-When antechamber uses the default locations, the service needs no
-configuration (see [Data paths](#data-paths)). To roll back, pause or remove
-the extension. It never writes to the OmO store, the antechamber registry, or
-the server.
-
-## Data paths
-
-By default the service reads:
-
-| What | Default |
-|---|---|
-| OmO agent directory | `~/.omo/agent`, then `~/.pi/agent` (both are scanned for tasks) |
-| antechamber state directory | `~/.config/antechamber`, then `~/.config/openchamber-pi-connector` (entries in the first win) |
-
-OpenChamber starts extension services with a minimal environment, so the
-service does not see `ANTECHAMBER_STATE_DIR` or the agent-directory variables
-(`OMO_CODING_AGENT_DIR`, `SENPI_CODING_AGENT_DIR`, `PI_CODING_AGENT_DIR`). If
-your deployment sets any of them, enter the same locations in the panel's
-**Data paths** popover (the sliders icon). They are saved in the extension's
-OpenChamber storage.
-
-## How it works
-
-See [docs/DESIGN.md](docs/DESIGN.md) for the data model, the layout, and the
-security boundary. In short:
-
-```
-panel (sandboxed iframe) ──serviceRequest GET /graph?session=ses_…──▶ OpenChamber host
-      ▲   openSession / setBadge / onSession                         │ loopback + bearer
-      │                                                              ▼
-      └──────────────── JSON graph ◀──────────── service/main.js (Node, read-only)
-                                                   reads ~/.omo/agent/projects/*/senpi-task/tasks/*.json
-                                                   and antechamber's sessions.json
-```
-
-## Development
-
-The extension is part of the antechamber repository's toolchain. All
-commands run from the repository root:
-
-| Command | What it covers for the extension |
-|---|---|
-| `npm run build:extension` | bundles `src/panel.ts` into `panel/main.js` (browser IIFE) and `src/service-main.ts` into `service/main.js` (Node ESM) with esbuild |
-| `npm test` | runs `extensions/*/test/*.test.ts` alongside the server tests |
-| `npm run typecheck` | checks `extensions/omo-dag/tsconfig.json` (DOM + Node) after the server |
-| `npm run lint` / `npm run format:check` | Biome, same rules as the rest of the repository |
-
-The sources are:
-
-- `src/graph.ts`: task records to graph, plus input validation;
-- `src/layout.ts`: columns, rows and edge routing;
-- `src/store.ts`: cached disk reads;
-- `src/service.ts`: HTTP;
-- `src/poller.ts`: the refresh loop, which runs one request at a time and
-  drops stale answers after a session or path change;
-- `src/panel.ts` and `panel/index.html`: the UI.
-
-`test/connector-parity.test.ts` imports antechamber's own `ocIdFor` and
-`SessionRegistryEntry`, so a change to session ids or registry fields on the
-server side fails the test suite rather than breaking the graph silently.

package/extensions/omo-dag/package.json

@@ -1,33 +0,0 @@
-{
-  "name": "antechamber-omo-graph",
-  "version": "1.0.41",
-  "description": "OpenChamber extension: live, interactive graph of the OmO sub-agents behind the current session",
-  "private": true,
-  "type": "module",
-  "license": "MIT",
-  "openchamber": {
-    "apiVersion": 1,
-    "engines": {
-      "openchamber": ">=1.22.0"
-    },
-    "contributes": {
-      "panel": {
-        "id": "omo-dag",
-        "name": "OmO Graph",
-        "icon": "icon.svg",
-        "entry": "panel/index.html"
-      },
-      "page": {
-        "entry": "panel/index.html",
-        "title": "OmO Graph"
-      },
-      "capabilities": [
-        "sessions"
-      ],
-      "service": {
-        "entry": "service/main.js",
-        "runtime": "host"
-      }
-    }
-  }
-}