Proposal: Web UI similar to Vibe Kanban (remote access instead of / alongside Electron)

[usmanovbf]

Right now Auto-Claude is tightly coupled to the Electron UI, which makes it hard to access and control from other devices (for example, from a smartphone over the Internet). Tools like Vibe Kanban demonstrate a different pattern: a web UI that can be opened from any browser while agents and code operations still run locally on the user’s machine.[1][2]

The proposal is to either rewrite the current UI as a web UI or add a new web UI alongside the existing Electron app:

1. Full web UI (replace Electron)

   • Move the main interface (tasks, logs, diff/review, configuration, monitoring) into a browser-based app that talks to a local Auto-Claude backend over HTTP/WebSocket.
   • Run the backend locally, but allow users to put it behind a VPN / SSH tunnel / reverse proxy so that they can securely connect from a phone or tablet over the Internet, similar to how Vibe Kanban runs locally but is accessed in a browser.[1]

2. Alternative web UI (keep Electron)

   • Keep Electron for users who prefer a desktop app, but factor out the UI into a separate web frontend that can also be served headless.
   • Electron would just wrap this web app, while the same UI could be opened from a normal browser (e.g., via a --web-ui flag or a config option).[2]

Why this would help

• Remote control of long-running sessions on a home/office machine from a smartphone or tablet via a secure URL.
• No need to install Electron on every device; any modern browser becomes a first-class client.
• Easier integration into existing dev environments (reverse proxy under a subdomain, add auth, integrate with other tools and dashboards).
• Aligns with the direction of tools like Vibe Kanban: local engine + HTTP API + web UI, which also makes it easier to evolve the product and swap/improve agent backends over time.[1]

Rough architecture idea

• Expose Auto-Claude’s core as a backend service with a clear API (REST/WebSocket/Server-Sent Events) for tasks, runs, logs, diff/review, and configuration.
• Implement a SPA web UI (React/Vue/Svelte/…) that consumes this API; optionally embed it inside Electron for users who like a desktop window.
• Provide configuration for bind address, port, and authentication to support secure remote access setups.