September 24, 2026
OpenCode can be run from another interface: OpenChamber 2.0 picks up settings immediately
On 23 September, OpenChamber 2.0 on OpenCode v2 began applying skills, agents, MCP servers, and plugins immediately after saving. The interface gained Code Mode, web search cards, and a stats page. OpenChamber costs $0; models are paid for with the user's own provider keys.

dax
@thdxr
The OpenCode server protocol underpins everything we do. It lets other developers build their own interfaces, such as OpenChamber, and turn them into polished, feature-rich products. We expect more of these interfaces as people begin exploring what they want from tools for working with agents.
OpenChamber 2.0 is out, on OpenCode v2. Skills, agents, MCP servers and plugins now apply the moment you save them. No restarts. My restart button is unemployed. Plus Code Mode, web search cards and a stats page. https://openchamber.dev/blog/opencode-v2/
· 6.6K views
[OpenCode] runs agents for coding, while OpenChamber gives them a dedicated interface. Previously, changes to skills, agents, MCP servers, and plugins required restarting OpenChamber. Version 2.0 now picks them up after saving.
A server nearby. The `opencode serve` command starts an HTTP server without an interface on `127.0.0.1:4096`. OpenCode serves OpenAPI 3.1 at `http://<hostname>:<port>/doc` for client generation and type inspection. Allowed CORS origins are added with the repeatable `--cors` flag.
Access to the server is protected by `OPENCODE_SERVER_PASSWORD`: HTTP Basic Auth uses the username `opencode`. The OpenChamber authors chose OpenCode for its open source nature, API, and extensibility.
The OpenChamber CLI and web version require Node.js 22+ and the OpenCode CLI installed. Install it with `curl -fsSL https://raw.githubusercontent.com/openchamber/openchamber/main/scripts/install.sh | bash`, then run `openchamber --ui-password <password>`.
At startup, OpenChamber first reuses its own server, then looks for an external one, then OpenCode on port 4096, and finally starts a server itself. To connect to an already running OpenCode, use `OPENCODE_HOST=http://localhost:4096 OPENCODE_SKIP_START=true openchamber`; `OPENCODE_HOST` needs a port without a path.
The OpenCode authors expect more interfaces on top of the server protocol as developers start building agent tools around their own way of working.
Source
