// the find
siteboon/claudecodeui
Use Claude Code, OpenCode, Cursor CLI, and Codex on mobile and web with CloudCLI (aka Claude Code UI). CloudCLI is a free open source webui/GUI that helps you manage your Claude Code session and projects remotely.
A web and mobile UI that wraps Claude Code, Cursor CLI, Codex, and OpenCode so you can drive AI coding agents from a browser instead of a terminal. Self-hostable via npx or Docker, or pay €7/month for their managed cloud tier. Aimed at developers who want to kick off long agent runs and monitor them from their phone or a remote machine.
The provider abstraction is well thought out — each CLI (Claude, Cursor, Codex, OpenCode) gets its own auth, sessions, MCP, models, and skills provider under a common interface, which makes adding a new one surgical rather than a global change. The plugin system is real: custom tabs with their own Node.js backend, installed from a git URL, communicating over a documented RPC. It reads and writes the same ~/.claude config that Claude Code uses natively, so nothing is duplicated and you don't end up with two sources of truth for MCP servers. Docker sandbox support for hypervisor-level isolation is a sensible addition if you're running agents against untrusted repos.
The server is a mix of plain JavaScript and TypeScript files — newer modules are typed, older routes like server/routes/agent.js and server/claude-sdk.js are not, so you get no safety net exactly where the most complex logic lives. The security story is thin for something that proxies shell access over the network: tools are disabled by default (good), but the auth middleware is a single JS file and the README basically says 'enable selectively' without addressing what happens when you expose this to the open internet. The AGPL-3.0 license is load-bearing: if your company modifies this and runs it internally as a service, you are technically required to publish those modifications — most legal teams will flag this. The Electron desktop app, cloud SaaS tier, npm package, and Docker sandbox all live in the same repo with separate CI pipelines for each, which is a maintenance surface area that will compound as features diverge.