- Home
- AI Computer Use Agents
- Screenbox
Screenbox
What it is
Screenbox provides self-hosted virtual desktops for AI agents, 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, clicking, typing, shell access, file operations, and clipboard control. Screenbox connects to MCP clients such as Claude Desktop, Claude Code, and Cursor through stdio, streamable HTTP, or SSE. Its dashboard supports live desktop viewing, agent management, snapshots, knowledge browsing, and session logs. Users can save and restore desktop state, including files and browser sessions, or clone desktops from templates. Session action logs can be compiled into reusable facts for future screenshot and look responses. Users can watch activity through RDP or noVNC and take mouse and keyboard control. Desktops run in Docker containers with memory limits, network isolation, and no bind mounts, but the maker cautions that these are not hardened sandboxes. The software runs on Linux with native Docker, macOS with Docker Desktop, and Windows with WSL2. Each desktop uses about 2 GB RAM and needs no GPU.
For and against
For
- Provides 21 MCP tools across more than 100 actions
- Includes Chromium and desktop applications
- Users can watch agents and take control
- Supports desktop snapshots and templates
- Maker says self-hosted software sends no telemetry
Against
- Docker containers are not hardened sandboxes
- Each desktop uses about 2 GB RAM
- Maker advises against exposing the MCP API publicly
The verdict
Screenbox combines agent-operated desktops with session visibility, snapshots, and human control. Its container isolation is not presented as a hardened sandbox, and the maker recommends restricting MCP API access.
Who it suits
Screenbox may suit people building or supervising AI-agent workflows that need browser and desktop app access. It is self-hosted and supports Linux, macOS, and Windows deployments.
Plans and prices
Self-hosted
AGPL-3.0 open-source software · Runs on your own infrastructure
Read 7 Oct 2026 · screenbox.dev
On the record
- Automation
- It offers 21 MCP tools across more than 100 actions, including screenshots, OCR, clicking, typing, shell, file I/O, and clipboard operations.screenbox.dev · read 7 Oct 2026
- Browser and apps
- Each desktop includes real Chromium with DevTools and extensions, plus desktop applications such as file managers, terminals, and office tools.screenbox.dev · read 7 Oct 2026
- Dashboard
- The web dashboard provides live desktop viewing, agent management, snapshot controls, a knowledge browser, and session logs.screenbox.dev · read 7 Oct 2026
- Human oversight
- Users can watch agent activity through RDP or noVNC and take mouse and keyboard control.screenbox.dev · read 7 Oct 2026
- Integrations
- It connects to MCP clients including Claude Desktop, Claude Code, and Cursor, and supports stdio, streamable HTTP, and SSE transports.screenbox.dev · read 7 Oct 2026
- Isolation
- Desktops run in Docker containers with memory limits, network isolation, and no bind mounts; the maker cautions that containers are not hardened sandboxes.github.com · read 7 Oct 2026
- Knowledge
- Screenbox can compile session action logs into reusable facts and inject that knowledge into future screenshot and look responses.screenbox.dev · read 7 Oct 2026
- Maker
- The Terms identify Dmytro Klymentiev as the product's developer and maintainer.screenbox.dev · read 7 Oct 2026
- 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.screenbox.dev · read 7 Oct 2026
- 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.screenbox.dev · read 7 Oct 2026
- Purpose
- Screenbox provides isolated virtual desktops with real browsers and desktop applications for AI agents.screenbox.dev · read 7 Oct 2026
- Resource management
- Idle desktops pause automatically, and acquired desktops can be released after a configurable time-to-live.screenbox.dev · read 7 Oct 2026
- 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.github.com · read 7 Oct 2026
- Snapshots
- Users can save and restore desktop state, including files and browser sessions, and clone desktops from templates.screenbox.dev · read 7 Oct 2026
- 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.github.com · read 7 Oct 2026