Screenbox
screenbox.dev
What it is
Screenbox gives AI agents isolated virtual desktops with real browsers and desktop applications. Each desktop includes Chromium with DevTools and extensions, plus tools such as file managers, terminals, and office applications. Agents can use 21 MCP tools across more than 100 actions, including screenshots, OCR, clicks, typing, shell access, file operations, and clipboard control. It connects to MCP clients including Claude Desktop, Claude Code, and Cursor through stdio, streamable HTTP, or SSE. A web dashboard supports live viewing, agent management, snapshots, session logs, and a knowledge browser. Users can save and restore desktop states, including files and browser sessions, and clone desktops from templates. Activity can be viewed through RDP or noVNC, with mouse and keyboard control available. Desktops run in Docker containers with memory limits, network isolation, and no bind mounts; the maker cautions that they are not hardened sandboxes. The software is self-hosted and open source under AGPL-3.0. The maker says deployment data stays on the user's infrastructure and the software sends no telemetry to Screenbox or third parties. It requires about 2 GB of RAM per desktop and no GPU; idle desktops pause automatically.
Spec sheet
- Purpose
- Screenbox provides isolated virtual desktops with real browsers and desktop applications for AI agents.Read 7 Oct 2026 · screenbox.dev
- Integrations
- It connects to MCP clients including Claude Desktop, Claude Code, and Cursor, and supports stdio, streamable HTTP, and SSE transports.Read 7 Oct 2026 · screenbox.dev
- Privacy
- The maker says the self-hosted software sends no telemetry or data to Screenbox or third parties, and deployment data remains on the user's infrastructure.Read 7 Oct 2026 · screenbox.dev
- Support
- The security policy asks vulnerability reports to be submitted through GitHub private vulnerability reporting and says it aims to acknowledge them within 48 hours.Read 7 Oct 2026 · github.com
- Maker
- The Terms identify Dmytro Klymentiev as the product's developer and maintainer.Read 7 Oct 2026 · screenbox.dev
- Automation
- It offers 21 MCP tools across more than 100 actions, including screenshots, OCR, clicking, typing, shell, file I/O, and clipboard operations.Read 7 Oct 2026 · screenbox.dev
- Browser and apps
- Each desktop includes real Chromium with DevTools and extensions, plus desktop applications such as file managers, terminals, and office tools.Read 7 Oct 2026 · screenbox.dev
- Dashboard
- The web dashboard provides live desktop viewing, agent management, snapshot controls, a knowledge browser, and session logs.Read 7 Oct 2026 · screenbox.dev
- Human oversight
- Users can watch agent activity through RDP or noVNC and take mouse and keyboard control.Read 7 Oct 2026 · screenbox.dev
- Isolation
- Desktops run in Docker containers with memory limits, network isolation, and no bind mounts; the maker cautions that containers are not hardened sandboxes.Read 7 Oct 2026 · github.com
- Knowledge
- Screenbox can compile session action logs into reusable facts and inject that knowledge into future screenshot and look responses.Read 7 Oct 2026 · screenbox.dev
- Platforms and requirements
- The maker lists Linux with native Docker, macOS with Docker Desktop, and Windows with WSL2; each desktop uses about 2 GB RAM and needs no GPU.Read 7 Oct 2026 · screenbox.dev
- Resource management
- Idle desktops pause automatically, and acquired desktops can be released after a configurable time-to-live.Read 7 Oct 2026 · screenbox.dev
- Security configuration
- The maker advises against exposing the MCP API publicly, recommends localhost or VPN access, and says API tokens are generated automatically by setup.Read 7 Oct 2026 · github.com
- Snapshots
- Users can save and restore desktop state, including files and browser sessions, and clone desktops from templates.Read 7 Oct 2026 · screenbox.dev
Plans and prices
Strong points and limits
Strong points
- Includes Chromium with DevTools and extensions.
- Supports snapshots and restoring desktop state.
- Users can observe agents and take control.
- Self-hosted software is listed as open source.
Limits
- Containers are not hardened sandboxes.
- Each desktop uses about 2 GB RAM.
- Maker advises against exposing the MCP API publicly.
Who it suits
Screenbox suits developers and teams connecting AI agents to desktop applications through MCP clients. It is for users able to self-host and configure access to the MCP API.
Verdict
Screenbox combines agent-controlled desktops with visibility, snapshots, and session logs. Its self-hosted model and explicit container caveat make deployment and API access configuration important considerations.
Where Specifiction places it
- AI Computer Use Agents#12 of 247.7