Discover and explore top open-source AI tools and projects—updated daily.
open-webuiYour computer, anywhere, in your browser
Top 93.3% on SourcePulse
<2-3 sentences summarising what the project addresses and solves, the target audience, and the benefit.> Open WebUI Computer (cptr) provides a comprehensive workstation experience accessible via any web browser, serving your entire computer—files, terminal, editor, Git, and running sessions—to any device. It targets users who need seamless access to their development environment from phones, tablets, or other computers, offering a unified platform for local work and AI agent integration. The primary benefit is a consistent, full-featured workstation accessible anywhere, anytime, without compromising local capabilities.
How It Works
Open WebUI Computer runs locally, exposing your machine's filesystem, shell, Git state, and applications through a web interface. Its core design prioritizes a mobile-first, touch-native experience with persistent sessions that survive disconnects, ensuring work continuity across devices. The system deeply integrates AI agents, allowing them to interact with your local environment by reading/writing files, executing commands, and browsing the web, leveraging your own API keys or subscribed coding agents. This approach offers a novel way to unify local development tools with powerful AI capabilities in a universally accessible format.
Quick Start & Requirements
pip install cptr or uvx cptr@latest run. Docker image ghcr.io/open-webui/computer:latest is also available.[mcp] or [all] can be installed via pip.http://localhost:8000.Highlighted Details
/v1/chat/completions.Maintenance & Community
The provided text mentions a call for contributions and hiring but lacks specific details on community channels (e.g., Discord, Slack), active contributors, or a public roadmap.
Licensing & Compatibility
Limitations & Caveats
The system provides full, un-sandboxed access to the host filesystem and shell, equivalent to an SSH session. This design is inherently insecure for shared instances, public internet exposure, or untrusted users due to the lack of per-user isolation or path sandboxing. It should be treated with the same security considerations as an open SSH port.
1 day ago
Inactive