feat(client): browser-based web UI to drive agents from any device (incl. mobile)

[michabbb]

Problem

The only human client today is the Tauri desktop app, so I can only use the workspace at a machine where it's installed. The relay is already headless and self-hostable -- I run it on a Linux server with no GUI -- but there's no way to actually use it from that server, or from my phone.

Agents don't keep office hours. When one posts a review or hits an approval gate at 11pm, I want to glance at my phone, read the thread, and approve -- not be tied to the one desktop where the app lives. Steering agents from anywhere is exactly what an agent workspace should nail, and right now the client is the bottleneck.

Proposal

A browser-accessible, mobile-friendly web UI that talks to the relay over the same WebSocket + REST surface the desktop app already uses -- enough to read channels, reply, react, and approve/deny workflow gates from any device.

I know the current React/Vite frontend is coupled to Tauri APIs (invoke, native binaries like buzz-acp), so it can't just be served in a browser as-is. A lighter web client focused on the read + reply + approve core would already cover most of the need; git hosting and local shell tools can stay desktop-only.

Why it matters

• Self-hosters get a usable client on the same box as the relay.
• Mobile access turns async agent work into "approved it from my phone."
• Share a URL instead of a per-platform desktop install.

Happy to help test on self-hosted Linux + mobile.

[Giszmo]

I'd like to support this feature request, too. People might be hesitant to install an app but visiting a website is very low commitment. The web version doesn't need to expose all features and could tease the user with buttons that don't work on the web version but tell the user to get the real thing.

I personally am very hesitant to install native apps on desktop because of the inferior sandboxing there. I'm happy to use mobile apps or web apps though.

[DanTup]

I'd like to see this too. I don't want the agents on my machine (for multiple reasons, including I want to be able to shut my machine down, and I want them in sandboxes I can control - such as OpenShell). With a web app I know there's no possibility anything is ever running on my machine. If I want it out the browser, I could install it as a PWA.

[tianheil3]

Self-host + headless server use case (👍)

Same pain: relay on a Debian box without GUI, want a browser shell as the human client (not Tauri Desktop). Agents can stay on the server via buzz-acp / future spawner (#2859); humans only need read/reply/@ from any browser.

Current web/ package in-tree is still closer to repo browser than a Desktop-parity channel UI — so this issue remains the right track for a real web client shell.

Related: multi-machine agent mention gaps (#3204 etc.) matter once the human is in the browser and agents run elsewhere.

[senatordev]

Strong +1. Our concrete use case is a Chromebook/Pixelbook as the lightweight daily control device, while the Buzz relay and persistent factory/CLI agents run 24/7 on a remote Linux host.

Today, we would need to run the full Buzz Desktop app remotely and access it through VNC. A browser client would let us keep the control plane in the cloud while using Buzz locally in Chrome—reading, replying and approving from the Pixelbook or phone without streaming an entire desktop.

Even a focused read/reply/approve MVP would unlock this architecture for us. Happy to help test it on ChromeOS with a remote Linux host.