antechamber 1.0.5 → 1.0.7

package/CHANGELOG.md

@@ -7,10 +7,20 @@ and this project uses [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [1.0.7] - 2026-10-20
+
+- fix(session): defer registry snapshots for cached lookups (#54)
+
+## [1.0.6] - 2026-10-20
+
+- docs: integrate the OmO Work extension across the docs (#55)
+
 ## [1.0.5] - 2026-10-20
 
 ### Fixed
 
+- Avoid copying the entire session registry for cached session lookups, preventing session lists
+  from blocking transcript loading after startup.
 - Reduce startup CPU usage and boot delays for large session histories by committing restoration metadata
   in one registry write, while preserving restored costs, child sessions and independent registry writers.
 

package/README.md

@@ -27,7 +27,8 @@ 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.
+- 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).
 - 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.
@@ -37,12 +38,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.
-- An optional OpenChamber extension, **OmO Graph**, that draws the OmO
-  sub-agents behind the open session as a live, clickable graph (see
-  [OpenChamber extension](#openchamber-extension-omo-graph)).
-- An optional OpenChamber 2.x Work Status section, **OmO Work**, for the
-  session's todo phases, monitors, eval cells and background work (see
-  [OmO Work](#openchamber-extension-omo-work)).
+- 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.
 
 ## Supported backends
 
@@ -93,11 +92,13 @@ 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 [OmO Graph extension](#openchamber-extension-omo-graph):
-`setup` ends by printing its folder
-(`$(npm root -g)/antechamber/extensions/omo-dag`). In OpenChamber, open
-**Settings → Extensions → Add → Folder**, paste that path, and approve the two
-permissions it asks for. The folder is updated in place by `npm update -g`.
+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`.
 
 For an isolated OpenChamber instance, leaving your main settings untouched:
 
@@ -205,67 +206,88 @@ node dist/cli.js setup --profile ~/.config/antechamber-openchamber \
 The source launcher requires the built `dist/cli.js`. Pull updates, run
 `npm ci && npm run build`, and restart OpenChamber.
 
-`npm run build` also builds the OmO Graph extension; `setup` prints its folder
-(`$PWD/extensions/omo-dag`) to add in **Settings → Extensions → Add → Folder**.
+`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 extension: OmO Graph
+## OpenChamber extensions
 
-`extensions/omo-dag` is an OpenChamber extension that ships with antechamber
-and is built by `npm run build`. With the default OmO backend, it adds a rail panel
-showing the open session's orchestrator and every sub-agent OmO launched,
-grouped in waves:
+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.
 
-It reads OmO's task store and antechamber's session registry read-only,
-through a small local service that OpenChamber starts.
+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).
 
-Install it from OpenChamber's **Settings → Extensions → Add**, using whichever
-source fits where OpenChamber runs:
+### OmO Work
 
-| 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#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. 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
-
-`extensions/omo-work` adds an **OmO Work** section to OpenChamber 2.x's Work
-Status panel (OpenChamber 2.3.2 or newer; 1.x has no extension sections). For
-the open session it shows the OmO todo list grouped by phase, terminal
-monitors with their matched lines, detached eval cells with their output and a
-Stop button, background terminal sessions, and the goal continuation timer
-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 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:
+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).
 
-## OpenChamber extension: OmO Compatibility
+### OmO Compatibility
 
-`extensions/omo-compat` is a second, code-free extension for OpenChamber 1.24
-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 URL
-`https://github.com/eliottness/antechamber#extension/omo-compat`.
-It asks for no permissions. Details:
+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
@@ -377,6 +399,8 @@ provenance and creates the GitHub release from the CHANGELOG. See
 - [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
 
 ## Credits
 

package/dist/session-store.js

@@ -385,8 +385,10 @@ export class SessionStore {
         this.file = join(dir, "sessions.json");
     }
     load() {
-        if (this.batchState !== undefined)
+        if (this.batchState !== undefined) {
+            this.batchState.entries ??= structuredClone((this.entries ??= this.readEntries()));
             return this.batchState.entries;
+        }
         if (this.entries !== undefined)
             return this.entries;
         this.entries = this.readEntries();
@@ -457,7 +459,7 @@ export class SessionStore {
     mutate(change) {
         if (this.batchState !== undefined) {
             this.batchState.changes.push(change);
-            change(this.batchState.entries);
+            change(this.load());
             return;
         }
         this.withRegistryLock(() => {
@@ -472,7 +474,7 @@ export class SessionStore {
         if (this.batchState !== undefined)
             return action();
         const changes = [];
-        const batch = { entries: structuredClone(this.load()), changes };
+        const batch = { entries: undefined, changes };
         this.batchState = batch;
         try {
             const result = action();

package/extensions/omo-compat/package.json

@@ -1,6 +1,6 @@
 {
   "name": "antechamber-omo-compat",
-  "version": "1.0.5",
+  "version": "1.0.7",
   "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

@@ -31,6 +31,10 @@ sessions on OmO.
 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

package/extensions/omo-dag/package.json

@@ -1,6 +1,6 @@
 {
   "name": "antechamber-omo-graph",
-  "version": "1.0.5",
+  "version": "1.0.7",
   "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

@@ -64,7 +64,8 @@ section (sandboxed iframe) --serviceRequest /status?session=ses_...--> OpenChamb
 `antechamber serve` writes `<state dir>/run/<pid>.json` (mode 0600) with its
 URL and a random token that opens only the `/antechamber/work-status` routes. The service
 picks the running server whose agent holds the session and relays the snapshot
-and the Stop and Fire now actions. It keeps no state. See
+and the Stop and Fire now actions. It keeps no state. See [docs/DESIGN.md](docs/DESIGN.md) for the snapshot, refresh,
+server choice and security boundary, and
 [docs/architecture.md](../../docs/architecture.md#omo-work-status-section) for
 where each piece of data comes from in OmO.
 

package/extensions/omo-work/docs/DESIGN.md

@@ -0,0 +1,117 @@
+# OmO Work: design
+
+OmO Work is an OpenChamber 2.x Work Status section for the background work of
+the open session. This document covers its parts, its data, its security
+boundary and its limits. Where each field comes from in OmO is documented in
+[docs/architecture.md](../../../docs/architecture.md#omo-work-status-section).
+
+## Parts
+
+```
+OpenChamber Work Status panel
+  └─ section frame (status/index.html + status/main.js, sandboxed iframe)
+       │ host.serviceRequest  GET /status, GET /eval, POST /eval/stop, POST /goal/fire
+       ▼
+OpenChamber host ── loopback + OPENCHAMBER_SERVICE_TOKEN ──▶ service/main.js (Node, on the host)
+                                                              │ reads <state dir>/run/<pid>.json
+                                                              │ Bearer <run token>
+                                                              ▼
+                                         antechamber  /antechamber/work-status/<session>[...]
+                                                              │ snapshot from its bridges,
+                                                              ▼ eval_cells.* / goal RPC to OmO
+                                                         omo --mode rpc
+```
+
+- **Manifest**: `contributes.statusSection` with its own entry, a host
+  `service`, and a `panel` block with no entry. OpenChamber 2.x's manifest
+  parser requires a `panel` object, but without `panel.entry` there is no rail
+  icon or panel; the section is the only surface.
+- **Frame** (`src/status.ts`, `src/view.ts`): renders the snapshot. It follows
+  the open session through `host.onSession`, sizes itself through
+  `host.setHeight`, and publishes one host header control, **Data path**, when
+  the host supports status controls.
+- **Service** (`src/service.ts`, `src/discovery.ts`): stateless relay. It finds
+  running antechamber servers through their run records and forwards the
+  frame's requests.
+- **Adapter** (`src/work-status.ts` in antechamber): builds the snapshot and
+  runs the actions.
+
+## Snapshot
+
+`GET /antechamber/work-status/<session>` answers one JSON object, version 1:
+
+| Field | Content |
+|---|---|
+| `live` | the session's agent process is running; peek, Stop and Fire now need it |
+| `todo` | todo phases in OmO's order, each `{name, tasks: [{content, status}]}`, status `pending`, `in_progress`, `completed` or `cancelled` |
+| `monitors` | live watches (newest first), then the five most recently ended, each with its last 20 matched lines and, once ended, a readable reason |
+| `evalCells` | detached eval cells from `eval_cells.list`, or from the codemode wake source when the list is unavailable (`evalCellsListed: false`) |
+| `background` | background terminal sessions whose process is alive |
+| `goal` | the goal continuation timer (`armed`, `kind`, `dueAtMs`) and the wake-source counts it waits on, or `null` |
+| `wakeSources` | other active wake sources without a dedicated view |
+
+The frame checks the envelope (`src/model.ts`) and imports these types from the
+adapter, so a shape change on either side fails the typecheck.
+
+## Refresh
+
+The frame polls `/status` one request at a time:
+
+- every 1.5 s while anything can change on its own (a live monitor, a running
+  or queued cell, a background session, an armed timer, a task in progress);
+- every 5 s otherwise, and while the page is hidden;
+- every 10 s after an error, keeping the last snapshot on screen with the
+  error above it.
+
+A session switch bumps a generation counter, so a late answer for the previous
+session is dropped. Elapsed times and countdowns tick every second from the
+snapshot without refetching. An open eval cell's output is re-read on each
+poll while the cell runs, and once more when its state changes, so a finished
+cell shows its last lines.
+
+The adapter caches `eval_cells.list` for one second per session, so several
+open sections cost one RPC.
+
+## Choosing the server
+
+Several antechamber servers can run at once, and each can answer for a session
+it only knows from disk. For `/status`, the service asks the servers in order,
+newest first, and prefers the first answer with `live: true`, else the first
+successful one. It remembers which server answered for each session and sends
+that session's actions there.
+
+Run records without a `token` (older antechamber versions) and records of dead
+processes are skipped. A wildcard bind address (`0.0.0.0`, `::`) is dialed on
+loopback.
+
+## Security boundary
+
+- **Token scope**: `serve` generates a random 256-bit token at start and writes
+  it into `<state dir>/run/<pid>.json` (file 0600, directory 0700). The adapter
+  accepts it as `Authorization: Bearer <token>` only when the normalized path
+  starts with `/antechamber/work-status/`, so dot segments, `%2e` and
+  backslashes cannot reach other routes. It never replaces the server password
+  for anything else.
+- **Who can read it**: only processes running as the same user, which can
+  already read antechamber's state directory and drive OmO directly.
+- **Frame**: the sandboxed iframe holds no token. It reaches the service only
+  through the host, which adds its own per-service token. All text from OmO is
+  inserted with `textContent`, never as HTML.
+- **Inputs**: session IDs must match `ses_[0-9A-Za-z]+` and cell IDs
+  `[\w.:-]{1,128}`, in both the service and the adapter. Output peeks are
+  capped at 64 KiB.
+- **Actions**: Stop and Fire now map to OmO's own RPC requests
+  (`eval_cells.stop`, `goal_continuation_fire_now`). The extension kills no
+  process itself.
+
+## Limits
+
+- No Stop for monitors or background terminal sessions, and no continuation
+  holds: OmO exposes neither over RPC.
+- Eval cells need OmO's codemode. Without it, or while the agent process is
+  stopped, the section shows the cells OmO last reported, without output or
+  Stop.
+- Background sessions come from OmO's terminal manifest, which OmO writes on
+  start and exit; their command is shown but not their output.
+- The service must run on the machine that runs antechamber, since it reads
+  the run records.

package/extensions/omo-work/package.json

@@ -1,6 +1,6 @@
 {
   "name": "antechamber-omo-work",
-  "version": "1.0.5",
+  "version": "1.0.7",
   "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.5",
+  "version": "1.0.7",
   "description": "OpenCode-compatible HTTP/SSE server that lets OpenChamber drive the pi coding agent (and OmO) over RPC",
   "type": "module",
   "license": "MIT",
@@ -40,6 +40,7 @@
     "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",