ACP UI supports Web Client! Connect to any remote ACP agent from browser

Source: Dev.to

Overview

A quick update on the ACP UI side project: the UI now works directly in any web browser. No installation, no app store—just open the URL and connect to any remote ACP‑compatible agent over WebSocket.

URL:

Features

• Connect to any ACP‑compatible agent (Copilot, Claude Code, Codex, Gemini, Qwen, Auggie, Qoder, OpenCode, OpenClaw, etc.).
• Use the same UI across desktop browsers, mobile browsers, native desktop apps, iOS, and Android.
• Support for both ws:// (LAN) and wss:// (anywhere) connections.
• Manage multiple sessions, switch agent modes, select models, and view tool calls in real time.
• Built‑in Traffic Monitor to watch the raw ACP protocol for debugging.
• $ /ping heartbeat keeps the WebSocket alive through NAT and proxy idle timeouts.

Platforms

One client, six platforms—same chat, same sessions, same agents.

Connection Options

Because the hosted site uses HTTPS, browsers block plain ws:// connections (mixed‑content rule). Choose one of the following:

1. Easy (secure) – Front your local agent with a wss:// URL. Microsoft Dev Tunnels provides a free secure tunnel.
2. LAN‑only – Clone the repository and run npm run preview:web locally. Then connect via ws://<host>:3000/.

Both flows are documented in the repository.

Architecture

The UI is built with Vue. The same frontend code is reused across:

• Web – runs in a plain browser tab.
• Desktop – packaged with Tauri, which provides a native shell and system WebView.
• Mobile – uses WKWebView (iOS) or Android WebView.

The web build omits the local‑subprocess code path and communicates with remote agents exclusively over WebSocket.

Source Code

• GitHub (MIT License):

Issues, pull requests, and stars are very welcome. Have fun connecting to your favorite agent from literally anywhere!