Web Terminal plugin stuck on "Connecting..." spinner — WebSocket frame type not preserved in plugin proxy

[RobertWalther]

Image Variant

Full (latest / dev)

Image Tag / Version

latest

Host OS

Linux

What happened?

The Terminal tab (web-terminal plugin) shows a "Connecting... Starting shell session" spinner indefinitely and never displays a shell.

What did you expect?

The Terminal tab should open a working bash shell after connecting.

Steps to reproduce

1. Install the web-terminal plugin
2. Open any project session
3. Click the "Terminal" tab
4. Observe the spinner never resolves

Docker Compose / Run command

services:
    holyclaude:
      image: coderluii/holyclaude:latest
      container_name: holyclaude
      restart: unless-stopped
      shm_size: 2g
      cap_add:
        - SYS_ADMIN
        - SYS_PTRACE
      security_opt:
        - seccomp=unconfined
      ports:
        - "3001:3001"
      volumes:
        - ./data/claude:/home/claude/.claude
        - ./workspace:/workspace

Logs / Error output

[Plugins] WS proxy connected to "web-terminal" on port 42871

  (no further output — the ready message is received by the proxy but forwarded
  as a binary frame, so the browser never processes it and the spinner remains)

[RobertWalther]

Fix

One-line change in server/index.js inside handlePluginWsProxy:

Before:

upstream.on('message', (data) => {
    if (clientWs.readyState === WebSocket.OPEN) clientWs.send(data);
});

After:

upstream.on('message', (data, isBinary) => {
    if (clientWs.readyState === WebSocket.OPEN) clientWs.send(data, { binary: isBinary });
});

Confirmed working — applied this patch locally and the Terminal tab connects immediately.

[CoderLuii]

confirmed this is a bug in CloudCLI's websocket proxy. it forwards all messages as binary frames instead of preserving the original frame type, so the browser never processes the text-based ready message.

since we dont control CloudCLI directly, the fix will be patched on our side in the holyclaude image. your one-line fix is exactly right. will be in the next version.

in the meantime you can use the main session terminal in CloudCLI instead of the plugin tab as a workaround.

[CoderLuii]

Fixed in v1.1.3.

Patched both relay directions (upstream-to-client and client-to-upstream) since they both had the same issue. Pull the latest image and the terminal tab should connect immediately.