easi.run
easi.run is an AGPL-3.0 self-hosted browser runtime written in Rust that gives AI agents isolated Chrome sessions paired with a live browser view and built-in MCP/REST endpoints. Humans can step in from the session bar to complete logins, 2FA, or CAPTCHAs and hand control back to the agent.
Explore the workflow and limits ↓What to use it for
Use easi.run when agents need persistent or isolated Chrome sessions on your own Linux server with one-click human takeover for 2FA, passwords, or anti-bot prompts—without paying per-hour cloud browser fees.
Each session supports encrypted persistent profiles, CSS-selector DOM reads, file uploads/downloads, AV1/lossless-tile streaming, per-session proxies, and an embedded MCP server (plus REST API) for Claude Code, Codex, and other MCP hosts.
Good fit: teams operating Linux x86-64 servers who want self-hosted human-in-the-loop browser automation. Choose another tool if you need macOS/Windows native hosting or cannot run Docker with privileged network setup.
License and operating costs
- License:
AGPL-3.0-only(check copyleft obligations if modifying or offering the software as a network service). - Software price: no per-hour or per-session vendor billing when self-hosted.
- Your infrastructure costs: VPS/bare-metal compute, residential/HTTP proxies (if configured per session), and your AI host or model API keys remain separate.
Installation & privileged setup steps
Per README.md and install.sh, easi.run targets Linux x86-64 with Docker 28+. Always inspect install.sh before running it on a host:
curl -fsSLO https://easi.run/install.sh && less install.sh && bash install.sh
What the installer documents doing:
- Pulls pre-built CI container images by digest and adds Google Chrome from Google's signed repository.
- Runs a short-lived privileged Debian container using
nsenterto configure hostiptablesfirewall rules (blocking browser sessions from reaching host-local services) and TCP (fq/ BBR) settings. - Starts easi.run and automatically registers the
easiMCP server in Claude Code if present and unconfigured.
Security & operational caveats
- Privileged installer footprint: because
install.shmodifies host firewall and sysctl settings, run it on a dedicated VM or server after auditinginstall.shdirectly. - Persistent login encryption: saved session state is encrypted on disk with a key derived from your admin password; if you lose the password or a save fails during upgrades, session state cannot be recovered automatically.
- No blanket security certification: review
docs/security.md#boundariesand site terms before automating authenticated accounts.