antechamber 0.0.0-stage → 0.1.1

package/CHANGELOG.md

@@ -0,0 +1,166 @@
+# Changelog
+
+All notable changes to this project are documented in this file.
+
+The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project uses [Semantic Versioning](https://semver.org/).
+
+## [Unreleased]
+
+## [0.1.1] - 2026-10-14
+
+### Added
+
+- Sessions now report `cost` (USD) from OmO's per-message usage, live and from
+  history, on v1 session payloads and v2 session reads. Subagent sessions carry
+  their own cost, so OpenChamber's work-status panel shows the session total
+  with its session/subagents breakdown.
+
+### Fixed
+
+- `/compact` now shows progress and its result. The session turns busy while
+  OmO compacts, and the summary appears as a `/compact` turn with a summary
+  reply, live and after reload. The compact RPC now waits up to OmO's own
+  30-minute compaction budget instead of giving up after 60 seconds, which left
+  the compaction running unseen until a later abort reported it cancelled.
+- Reverting no longer adds a "Conversation reverted. Files were not changed."
+  card to the transcript; OpenChamber's own reverted-message dock (driven by
+  `session.revert`) already shows the state.
+- Sessions opened with a slash command (for example `/skill:plan Build the
+  importer`) now get a generated title. OmO skips titling slash-led prompts, so
+  the adapter passes the command's arguments as the native `sessionTitlePrompt`.
+
+## [0.1.0] - 2026-10-14
+
+First standalone release under the `antechamber` name.
+
+### Renamed
+
+This project was previously published as `openchamber-pi-connector`. The
+rename affects:
+
+- Package and CLI binary: `openchamber-pi-connector` / `opencode-pi` to
+  `antechamber` (`dist/cli.js`, bin name `antechamber`).
+- Launcher script: `bin/opencode-antechamber` is the new OpenChamber launcher;
+  `bin/opencode-pi` is kept as a deprecated shim that forwards to it, so
+  existing `settings.opencodeBinary` values keep working.
+- Environment variables: all settings now read the `ANTECHAMBER_` prefix
+  first (for example `ANTECHAMBER_PI_BINARY`, `ANTECHAMBER_STATE_DIR`,
+  `ANTECHAMBER_AGENT`, `ANTECHAMBER_IDLE_TIMEOUT_MS`, `ANTECHAMBER_MAX_LIVE`,
+  `ANTECHAMBER_DEBUG`). The previous `OCPI_` prefix is still accepted as a
+  deprecated fallback; migrate at your own pace.
+- State directory: defaults to `~/.config/antechamber`. If that directory
+  doesn't exist yet but the legacy `~/.config/openchamber-pi-connector`
+  does, the legacy directory is used automatically so existing session
+  registries keep working across the upgrade. Move the directory manually
+  once you're ready to drop the fallback.
+- No action needed for most users: both the binary and environment variable
+  fallbacks mean an existing OpenChamber `settings.json` pointing at
+  `opencode-pi` keeps working unchanged.
+
+### Changed
+
+- OmO is now the default backend: antechamber spawns `omo` unless
+  `ANTECHAMBER_PI_BINARY` says otherwise, and the agent directory follows
+  OmO's resolution (`OMO_CODING_AGENT_DIR` > `SENPI_CODING_AGENT_DIR` >
+  `PI_CODING_AGENT_DIR`, default `~/.omo/agent`; `~/.pi/agent` when the backend
+  is `pi`). A standard OmO install is advertised as the `OmO` agent without
+  setting `ANTECHAMBER_AGENT`. Plain pi remains available as an opt-in,
+  best-effort backend (`ANTECHAMBER_PI_BINARY=pi`).
+
+### Added
+
+- OmO Graph, an OpenChamber extension in `extensions/omo-dag`. It draws the
+  OmO sub-agents behind the open session as a live graph:
+  - cards are grouped in waves and show each sub-agent's state, duration,
+    agent and model;
+  - hovering a card highlights its input and output edges;
+  - clicking a card opens the sub-agent's session.
+
+  The extension is built by `npm run build`, is covered by `npm test`,
+  typecheck and lint, and ships in the npm package. It reads OmO's task store
+  and the session registry read-only, through an OpenChamber-managed local
+  service.
+- `antechamber setup` ends by printing the bundled OmO Graph extension folder
+  to add in OpenChamber (Settings → Extensions → Add → Folder), and every
+  GitHub release attaches `antechamber-omo-graph.zip`, installable from
+  OpenChamber by URL
+  (`https://github.com/eliottness/antechamber/releases/latest/download/antechamber-omo-graph.zip`).
+- npm-first installation with `antechamber setup`: settings discovery,
+  isolated profiles, executable selection, timestamped backups, idempotency,
+  dry-run plans, and optional systemd user drop-ins with explicit restart.
+- Read-only `antechamber doctor` diagnostics with text/JSON output, backend
+  checks, agent/state directory checks, OpenChamber wiring and pidfd capability.
+- Explicit `serve`, `setup`, `doctor`, `version`, and `help` commands. Package
+  versions now come from `package.json`; the OpenChamber `--version` probe
+  keeps advertising `opencode v2.0.18`.
+- Public npm publication configuration with provenance and an executable
+  built CLI, plus installation, upgrade and rollback documentation.
+- Tag-driven release workflow: a `vX.Y.Z` tag runs the checks, publishes to
+  npm with provenance (trusted publishing or `NPM_TOKEN`) and creates the
+  GitHub release from this file. See [docs/releasing.md](docs/releasing.md).
+- Security hardening: optional HTTP Basic auth (`OPENCODE_SERVER_PASSWORD`),
+  `Origin` checks for unauthenticated servers, a non-loopback-bind guard, and
+  request/SSE/search limits. See [docs/configuration.md](docs/configuration.md#security).
+- OpenCode v2 API support (`@opencode-ai/sdk/v2`), alongside the original v1
+  surface, covering the endpoints OpenChamber >= 2.0.4 depends on.
+- [OmO](https://github.com/omo-ai) backend support (a pi-compatible
+  coding-agent distribution, aka senpi / oh-my-pi), including OmO-specific
+  session-tree fork/revert/unrevert, subagent and task cards, todo bridging,
+  and thinking-level mapping.
+- Session fork, revert, and unrevert backed by the agent's native session
+  tree rather than a filesystem snapshot.
+- Subagent and task cards rendered as native OpenChamber tool parts.
+- Approval and question bridging through the agent's extension-UI protocol.
+- Thinking-level selection surfaced through OpenChamber's model picker.
+- Shell run cards (user-invoked `!command` execution) with cancellation.
+- Session diff endpoint returning a unified patch independent of
+  OpenChamber's own git integration.
+- Session persistence and revival across connector restarts.
+- Idle session reaping and a configurable cap on concurrent live agent
+  processes (lifecycle caps).
+
+### Fixed
+
+- Slash commands sent through `POST /session/:id/command` (for example
+  `/skill:<name> ...`) now reuse OpenChamber's client `messageID`, so the user
+  message no longer appears twice in the chat.
+- With a server password configured, requests carrying a non-loopback
+  `Origin` (forwarded by OpenChamber's proxy for LAN browsers and the desktop
+  app) are no longer rejected with 403; the password is the boundary.
+- Turn statistics now use the native assistant stop reason independently of
+  usage, normalize tool-call finishes, and preserve tokens, cost, errors, and
+  response-model attribution in v1 and v2 history. Restored messages retain
+  their provider-to-append duration when valid timestamps are available.
+- Native session titles replace provisional first-message titles and persist
+  through reload and revival. Explicit user titles win over delayed native
+  generation; scans read the latest native name even beyond the transcript
+  head limit. Both OmO and Senpi client capability variables now advertise
+  `auto_title_sessions` and `question` while preserving inherited capabilities.
+  Historical title generation for old unnamed sessions is deferred to a
+  follow-up; existing native names are restored without adding a conversation
+  turn.
+- Busy prompts now carry native steer/follow-up admission behavior and stable
+  client message IDs instead of waiting behind a running turn until the RPC
+  timeout. v1 defaults to steering; v2 validates and honors steer/queue delivery,
+  publishes inbox acceptance and consumption, and restores durable pending
+  input without duplicating consumed user cards or changing assistant parents.
+- Structured `ask_user_question` requests now remain visible after a
+  nonblocking tool finishes. OpenChamber 1.24.2 receives v1 question
+  events and lists; OpenChamber 2.x receives native forms, including
+  multiselect, custom text, partial answers, comments, and cancellation.
+  Replies use correlated native acknowledgments rather than sending a
+  duplicate prompt.
+- Pending native questions hydrate on session revival with stable public
+  IDs and refreshed connection IDs. Dormant-session dangling-question
+  scanning without revival is deliberately omitted: those questions enter
+  lists only after revival. Native repeated-crash recovery limitations
+  remain; no native recovery code is changed.
+
+### History
+
+Everything before this release lived under the `openchamber-pi-connector`
+name, originally authored by qingzhu521 (xiuli.qz) as a minimal pi-backed
+OpenCode-API adapter for OpenChamber, and MIT-licensed. This fork retained
+that license and extended the project substantially; see the README's
+Credits section.

package/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2026 openchamber-pi contributors
+Copyright (c) 2026 antechamber contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,3 +1,317 @@
-# Temporary Holding Version
+# antechamber
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+A local OpenCode-compatible HTTP/SSE server that lets [OpenChamber](https://github.com/openchamber/openchamber) drive [OmO](https://github.com/code-yeongyu/oh-my-openagent) instead of OpenCode. Plain [pi](https://github.com/badlogic/pi-mono) also works as an opt-in backend.
+
+[![CI](https://github.com/eliottness/antechamber/actions/workflows/ci.yml/badge.svg)](https://github.com/eliottness/antechamber/actions/workflows/ci.yml)
+[![License](https://img.shields.io/github/license/eliottness/antechamber?style=flat&labelColor=100F0F&color=205EA6)](./LICENSE)
+
+## What it is
+
+OpenChamber only speaks the OpenCode HTTP/SSE API. OmO (and pi, which it
+builds on) are headless agents with their own RPC protocol (JSONL over stdio). antechamber sits
+between them: it implements the subset of the OpenCode API that OpenChamber
+actually uses, and translates every call into an OmO RPC session.
+
+```
+OpenChamber (UI)  --OpenCode API (HTTP/SSE)-->  antechamber  --JSONL/stdio-->  omo --mode rpc
+                                                                                (one process per session)
+```
+
+No fork of OpenChamber or pi is required. Point OpenChamber at antechamber as
+an **external OpenCode server** and sessions run on OmO.
+
+## Features
+
+- Session create/list/rename/archive/delete, prompt streaming (text and
+  reasoning deltas), and abort, mapped onto pi/OmO RPC sessions.
+- 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.
+- 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.
+- Session diff endpoint (unified patch) independent of OpenChamber's own git
+  integration.
+- Session persistence and revival across connector restarts, with explicit
+  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)).
+
+## Supported backends
+
+| Backend | Status |
+|---|---|
+| [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)).
+
+## Compatibility
+
+| OpenChamber | API | Status |
+|---|---|---|
+| >= 2.0.4 | v2 (`@opencode-ai/sdk/v2`) | primary target; antechamber advertises `opencode v2.0.18` on `--version` |
+| 1.24.x | v1 | supported |
+| other versions | - | not tested |
+
+OpenChamber changes which OpenCode API calls it makes between releases. If a
+feature breaks on a newer OpenChamber, run `npm run smoke` to see which check
+failed, then open an issue with the output. See
+[docs/api-surface.md](docs/api-surface.md) for the exact endpoints antechamber
+implements.
+
+## Quick start
+
+Needs Node.js 22+ and OmO's `omo` command on PATH (`bun add -g omo-ai`).
+
+```bash
+npm i -g antechamber
+# or: bun add -g antechamber
+antechamber doctor
+antechamber setup
+```
+
+The first npm publication (0.1.0) is part of the
+[release process](docs/releasing.md). If it is not on the registry yet, use
+[From source](#from-source) below.
+
+`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`.
+
+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`.
+
+For an isolated OpenChamber instance, leaving your main settings untouched:
+
+```bash
+antechamber setup --profile ~/.config/antechamber-openchamber
+# setup prints the command for this profile:
+OPENCHAMBER_DATA_DIR=~/.config/antechamber-openchamber openchamber serve --port 57124
+```
+
+For a systemd-managed OpenChamber, also capture the shell's PATH and the
+absolute OmO executable in a user service drop-in:
+
+```bash
+antechamber setup --systemd
+# default unit: openchamber.service; another unit: --systemd my-openchamber.service
+systemctl --user daemon-reload && systemctl --user restart openchamber.service
+# or explicitly let setup run those commands:
+antechamber setup --systemd --restart
+```
+
+`--pi-binary /absolute/path/to/omo` overrides backend discovery for the drop-in.
+Other drop-ins setting `ANTECHAMBER_*` or `OCPI_*` produce a warning: later
+files can override the generated configuration. `setup` never runs systemctl
+unless `--restart` is passed.
+
+OpenChamber spawns whatever `settings.opencodeBinary` points at as
+`serve --hostname H --port P`, waits for the stdout line
+`opencode server listening on <url>`, then health-checks `/global/health`.
+The installed `antechamber` bin implements this contract itself, including the
+`--version` compatibility probe. `bin/opencode-antechamber` is only needed for
+source checkouts; `bin/opencode-pi` remains a deprecated compatibility shim.
+
+You can also run antechamber directly, outside of OpenChamber's managed
+lifecycle:
+
+```bash
+antechamber --port 4096 --host 127.0.0.1 --directory /path/to/project
+# or, OpenCode-compatible:
+antechamber serve --hostname 127.0.0.1 --port 4096
+```
+
+## Commands
+
+| Command | Purpose / options |
+|---|---|
+| `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`. |
+| `antechamber doctor` | Read-only Node, backend, agent/state directories, teardown, OpenChamber and auth checks; `--json`, `--settings <file>`, `--profile <dir>`. Exits 1 on any FAIL; warnings do not fail. |
+| `antechamber version` | Package version plus OpenCode API contract version. `--version`/`-v` deliberately print exactly `opencode v2.0.18` for OpenChamber. |
+| `antechamber help` | Usage and options; also `--help`/`-h`. |
+
+## Upgrade, uninstall and rollback
+
+```bash
+npm update -g antechamber
+# or: bun add -g antechamber
+```
+
+Restart OpenChamber, or `systemctl --user restart openchamber.service` for a
+managed service. Run `antechamber doctor` again. If the executable moved,
+rerun `antechamber setup`.
+
+To roll back wiring, copy the backup printed by setup over the settings file:
+
+```bash
+cp /path/settings.json.bak-antechamber-YYYYMMDDHHMMSS /path/settings.json
+```
+
+If you used `--systemd`, restore the printed `antechamber.conf` backup, or
+remove only that generated drop-in if there was no previous file. Then run
+`systemctl --user daemon-reload` and restart OpenChamber/the service. Restore
+the old `opencodeBinary` before uninstalling:
+
+```bash
+npm uninstall -g antechamber
+# or: bun remove -g antechamber
+```
+
+## From source
+
+```bash
+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"
+# isolated alternative:
+node 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
+`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**.
+
+## OpenChamber extension: OmO Graph
+
+`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:
+
+- 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.
+
+Install it from OpenChamber's **Settings → Extensions → Add**, using whichever
+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` |
+
+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:
+[extensions/omo-dag/README.md](extensions/omo-dag/README.md).
+
+## Configuration
+
+All settings are environment variables prefixed `ANTECHAMBER_`. The
+deprecated `OCPI_` prefix is still accepted as a fallback for existing
+deployments. Full reference, defaults, and units: [docs/configuration.md](docs/configuration.md).
+
+| Variable | Purpose |
+|---|---|
+| `ANTECHAMBER_PI_BINARY` | agent executable to spawn (default `omo`; set to `pi` for plain pi) |
+| `ANTECHAMBER_PI_ARGS` | extra whitespace-split args passed to that binary |
+| `ANTECHAMBER_STATE_DIR` | session registry directory |
+| `ANTECHAMBER_AGENT` | agent name override advertised to OpenChamber |
+| `ANTECHAMBER_IDLE_TIMEOUT_MS` | idle session reap timeout |
+| `ANTECHAMBER_MAX_LIVE` | cap on concurrent live agent processes |
+| `ANTECHAMBER_DEBUG` / `ANTECHAMBER_DEBUG_LOG` | request/event debug logging |
+
+## Security
+
+antechamber is a local development tool: by default it binds to loopback
+with no authentication, and it can run arbitrary shell commands on behalf of
+the agent. Treat it the same way you'd treat a local dev server with shell
+access, not a service to expose on a network.
+
+Hardening controls (full reference in [docs/configuration.md](docs/configuration.md#security)):
+
+- Optional HTTP Basic auth, matching OpenCode's own contract:
+  `OPENCODE_SERVER_PASSWORD` (plus `OPENCODE_SERVER_USERNAME`, default
+  `opencode`).
+- Without a password, requests carrying a non-loopback browser `Origin` are
+  rejected unless listed in `ANTECHAMBER_ALLOWED_ORIGINS`.
+- Binding to a non-loopback host requires a password, `ANTECHAMBER_ALLOW_INSECURE=1`,
+  or the `--insecure-no-auth` flag.
+- Request bodies are capped by `ANTECHAMBER_MAX_BODY_BYTES` (default 10 MiB);
+  SSE subscribers, file search and agent RPC frames have fixed bounds.
+
+## Platform notes
+
+Linux is the primary supported platform. OmO's private task-host teardown
+(killing detached supervisor processes antechamber spawned) needs Linux
+pidfds (`os.pidfd_open`, Linux 5.3+) and `python3` on PATH; Node has no pidfd
+API. On other platforms that teardown step is skipped with one warning instead
+of crashing; antechamber never falls back to signalling numeric PIDs. macOS is untested.
+
+## Limitations / non-goals
+
+- Not a reimplementation of OpenChamber's own platform features (scheduler,
+  relay, goals). Those stay in OpenChamber.
+- Not a way to use pi/OmO as an LLM provider inside OpenCode. pi/OmO are full
+  agents with their own loop; antechamber adapts at the session-protocol
+  level, not the model level.
+- Some OpenCode routes have no pi/OmO equivalent and are stubbed or return
+  `400`/`501` (OAuth-based provider auth, MCP connect/disconnect, session
+  share). See [docs/api-surface.md](docs/api-surface.md) for the exact list.
+
+## Development
+
+```bash
+npm run typecheck
+npm test
+npm run build
+```
+
+The smoke scripts (`npm run smoke`, `npm run omo-smoke`, `npm run probe`,
+`npm run model-smoke`, `npm run v2-smoke`) drive a real `omo` (or `pi`)
+process end to end and cost model tokens; they are not part of `npm test`
+and are not run in CI. See [docs/development.md](docs/development.md).
+
+Releases are cut by pushing a `vX.Y.Z` tag; CI then runs the checks,
+publishes to npm with provenance and creates the GitHub release from the
+CHANGELOG. See [docs/releasing.md](docs/releasing.md).
+
+## Docs
+
+- [docs/architecture.md](docs/architecture.md) - design and session-model mapping
+- [docs/api-surface.md](docs/api-surface.md) - OpenCode endpoints implemented, stubbed, or unsupported
+- [docs/configuration.md](docs/configuration.md) - full environment variable reference
+- [docs/development.md](docs/development.md) - source layout, testing, smoke scripts
+- [docs/backends/omo.md](docs/backends/omo.md) - OmO backend details (agent name, task hosts, transcripts)
+- [docs/releasing.md](docs/releasing.md) - versioning, tag-driven npm and GitHub releases
+
+- [extensions/omo-dag/README.md](extensions/omo-dag/README.md) - the OmO Graph OpenChamber extension ([design](extensions/omo-dag/docs/DESIGN.md))
+
+## Credits
+
+antechamber began as a fork of
+[openchamber-pi-connector](https://github.com/qingzhu521/openchamber-pi-connector)
+by qingzhu521 (xiuli.qz), released under the MIT license, and was substantially
+extended from there (OpenCode v2 API support, OmO support, session fork/revert,
+subagent and task cards, approvals, todos, thinking levels, shell runs, diffs,
+session persistence, lifecycle caps, and more).
+
+Also relies on [OpenChamber](https://github.com/openchamber/openchamber),
+[OmO](https://github.com/code-yeongyu/oh-my-openagent) by code-yeongyu, and
+[pi](https://github.com/badlogic/pi-mono) by badlogic / earendil.
+
+## License
+
+MIT. See [LICENSE](./LICENSE), which retains the original
+openchamber-pi-connector copyright notice alongside the antechamber one.

package/bin/opencode-antechamber

@@ -0,0 +1,18 @@
+#!/bin/sh
+# OpenChamber launcher: point `settings.opencodeBinary` (or $OPENCODE_BINARY)
+# at this file. OpenChamber runs `<binary> serve --hostname H --port P` and
+# `<binary> --version`; anything else is rejected.
+# Requires a build (`npm run build`) so that dist/cli.js exists.
+set -eu
+SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)"
+CLI="$SCRIPT_DIR/../dist/cli.js"
+if [ ! -f "$CLI" ]; then
+  echo "opencode-antechamber: $CLI not found; run 'npm run build' first" >&2
+  exit 1
+fi
+case "${1:-}" in
+  serve) shift; exec node "$CLI" serve "$@" ;;
+  --version|-v) exec node "$CLI" --version ;;
+esac
+echo "opencode-antechamber: unsupported command '${1:-}' (only 'serve' and '--version' are implemented)" >&2
+exit 1

package/bin/opencode-pi

@@ -0,0 +1,3 @@
+#!/bin/sh
+# Deprecated name kept for existing OpenChamber settings; use opencode-antechamber.
+exec "$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)/opencode-antechamber" "$@"

package/dist/agent-dir.d.ts

@@ -0,0 +1,6 @@
+/**
+ * Root directory of the coding agent's state. Mirrors OmO's own resolution
+ * (OMO_ > SENPI_ > PI_CODING_AGENT_DIR, default ~/.omo/agent); a plain pi
+ * backend defaults to pi's ~/.pi/agent instead.
+ */
+export declare function piAgentDir(env?: NodeJS.ProcessEnv, home?: string): string;

package/dist/agent-dir.js

@@ -0,0 +1,21 @@
+import { homedir } from "node:os";
+import { join } from "node:path";
+import { isPlainPi } from "./config.js";
+function expandLeadingTilde(path, home) {
+    if (path === "~")
+        return home;
+    if (path.startsWith("~/") || path.startsWith("~\\"))
+        return join(home, path.slice(2));
+    return path;
+}
+/**
+ * Root directory of the coding agent's state. Mirrors OmO's own resolution
+ * (OMO_ > SENPI_ > PI_CODING_AGENT_DIR, default ~/.omo/agent); a plain pi
+ * backend defaults to pi's ~/.pi/agent instead.
+ */
+export function piAgentDir(env = process.env, home = homedir()) {
+    const configured = [env.OMO_CODING_AGENT_DIR, env.SENPI_CODING_AGENT_DIR, env.PI_CODING_AGENT_DIR].find((value) => typeof value === "string" && value.trim() !== "");
+    if (configured !== undefined)
+        return expandLeadingTilde(configured.trim(), home);
+    return isPlainPi(env) ? join(home, ".pi", "agent") : join(home, ".omo", "agent");
+}

package/dist/agent-name.d.ts

@@ -0,0 +1,24 @@
+/**
+ * Agent-name detection: the adapter reports one OpenCode "agent" to the UI.
+ * Resolution order (<agent dir> is piAgentDir(), ~/.omo/agent by default):
+ *   1. ANTECHAMBER_AGENT env override
+ *   2. <agent dir>/../oh-my-pi.jsonc → orchestrator.agentName
+ *   3. <agent dir>/../omo.jsonc exists (an OmO install) → "OmO"
+ *   4. <agent dir>/settings.json packages containing oh-my-pi → "oh-my-pi"
+ *   5. "build" (plain pi)
+ * The result is memoized: config changes require an adapter restart.
+ */
+import { existsSync, readFileSync } from "node:fs";
+export declare function detectAgentName(env?: NodeJS.ProcessEnv, home?: string, fs?: {
+    readonly existsSync: typeof existsSync;
+    readonly readFileSync: typeof readFileSync;
+}): string;
+export declare function getAgentName(): string;
+/**
+ * Agent names the adapter publishes to OpenChamber's picker. pi has exactly one
+ * agent. The resolved pi name is published first so OpenChamber chooses it for
+ * new sessions; `build` remains a compatibility alias for existing sessions.
+ * Both names run the same pi agent — the requested agent name is not forwarded
+ * to pi. When pi's name already is `build` the list collapses to one.
+ */
+export declare function getExposedAgentNames(): string[];