antechamber 1.0.19 → 1.0.20

package/CHANGELOG.md

@@ -7,6 +7,15 @@ and this project uses [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [1.0.20] - 2026-10-26
+
+### Fixed
+
+- Work with OpenChamber 2.5.2, which refuses OpenCode older than 2.1.0 and showed an "Update OpenCode" screen
+  that never cleared. antechamber now reports OpenCode API 2.1.0, and `PATCH /api/session/{id}` accepts 2.1's
+  `archived: true|false`, so archiving and unarchiving from OpenChamber 2.5.2 take effect instead of answering 204
+  and changing nothing.
+
 ## [1.0.19] - 2026-10-25
 
 ### Fixed

package/README.md

@@ -57,7 +57,7 @@ another executable (see [docs/configuration.md](docs/configuration.md)).
 
 | OpenChamber | API | Status |
 |---|---|---|
-| >= 2.0.4 | v2 (`@opencode-ai/sdk/v2`) | primary target; antechamber advertises `opencode v2.0.20` on `--version` |
+| >= 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 |
 | other versions | - | not tested |
 
@@ -148,7 +148,7 @@ antechamber serve --hostname 127.0.0.1 --port 4096
 | `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.0.20` for OpenChamber. |
+| `antechamber version` | Package version plus OpenCode API contract version. `--version`/`-v` deliberately print exactly `opencode v2.1.0` for OpenChamber. |
 | `antechamber help` | Usage and options; also `--help`/`-h`. |
 
 ## Upgrade, uninstall and rollback
@@ -165,8 +165,8 @@ 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 shows an "OpenCode update" notice because antechamber
-reports OpenCode API 2.0.20, the minimum OpenChamber accepts. The notice names
+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

package/dist/routes-v2.js

@@ -510,9 +510,16 @@ export async function handleV2(services, req, res, url, path, method, directory)
             }
             case "PATCH ": {
                 const body = (await services.body(req));
+                // OpenCode 2.1 takes `archived: boolean` (repeating the current state is a no-op);
+                // older clients send `time.archived` as a timestamp, 0 to unarchive.
+                const archived = typeof body.archived === "boolean"
+                    ? body.archived
+                        ? (managed.info.time.archived ?? Date.now())
+                        : 0
+                    : body.time?.archived;
                 await services.sessions.update(sessionId, {
                     title: body.title,
-                    archived: body.time?.archived,
+                    archived,
                     metadata: sessionMetadata(body.metadata),
                 });
                 res.writeHead(204).end();

package/dist/version.d.ts

@@ -1,2 +1,2 @@
 export declare const ADAPTER_VERSION: string;
-export declare const OPENCODE_API_VERSION = "2.0.20";
+export declare const OPENCODE_API_VERSION = "2.1.0";

package/dist/version.js

@@ -10,4 +10,5 @@ if (typeof manifest !== "object" ||
 export const ADAPTER_VERSION = manifest.version;
 // OpenChamber parses --version as an OpenCode version and requires major 2.
 // This API contract version must not follow the npm package version.
-export const OPENCODE_API_VERSION = "2.0.20";
+// OpenChamber 2.5.2 requires 2.1.0, which added top-level `archived` to PATCH /api/session/{id}.
+export const OPENCODE_API_VERSION = "2.1.0";

package/extensions/omo-compat/package.json

@@ -1,6 +1,6 @@
 {
   "name": "antechamber-omo-compat",
-  "version": "1.0.19",
+  "version": "1.0.20",
   "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/package.json

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

package/extensions/omo-work/package.json

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