@fugood/bricks-cli 2.24.1-beta.3 → 2.24.2

package/README.md

@@ -270,6 +270,24 @@ Controls:
 
 When `bricks` is run without arguments in a non-TTY context such as Codex, CI, or shell pipelines, it prints help instead of launching Ink.
 
+### Desktop ACP Bridge
+
+Connect external ACP clients (e.g. [acpx](https://github.com/openclaw/acpx)) to the running CTOR Desktop app.
+
+```bash
+# Stdio mode (default) — pipes stdin/stdout ↔ ~/.bricks-project-desktop/acp.sock
+bricks desktop-acp-bridge
+
+# WebSocket mode — exposes the Unix socket as a WebSocket server
+bricks desktop-acp-bridge --ws
+bricks desktop-acp-bridge --ws --host 127.0.0.1 --port 8765
+bricks desktop-acp-bridge --ws --auth-token <secret>
+```
+
+In WebSocket mode each client connection opens a dedicated bridge to the ACP Unix socket. Messages are exchanged as newline-delimited JSON-RPC: one WS text frame per JSON-RPC message. When `--auth-token` is set (or `BRICKS_DESKTOP_ACP_BRIDGE_TOKEN` is exported), the server requires the matching `Authorization: Bearer <token>` header on the WebSocket upgrade request.
+
+> The default bind host is `0.0.0.0` — WebSocket mode is intended to expose ACP on the LAN. Always set `--auth-token` and only run on trusted networks. Use `--host 127.0.0.1` to restrict to localhost.
+
 ### Workspace Info
 
 ```bash
@@ -287,16 +305,6 @@ Configuration is stored in `~/.bricks-cli/config.json`:
 
 Use `bricks config show` to view current settings, `bricks config endpoint` to switch environments, or `bricks doctor --json` for a machine-readable health check.
 
-## Development
-
-```bash
-# Run locally
-node bin/bricks.js
-
-# Run with file watching
-bun dev
-```
-
 ## License
 
 UNLICENSED