Agent Zero v2.5 + Launcher: meet the Host Access Gateway

What shipped

Agent Zero Core and CLI v2.5, together with the new version of the Launcher, introduce the Host Access Gateway: a bridge between the sandboxed Docker environment and your real machine, embedded directly in the Launcher.

What problem it solves

Agent Zero runs containerized for safety. Until now, letting the agent access your host system required installing the A0 CLI, opening a terminal session, and authorizing each capability manually (/computer-use for the desktop, /browser host on for the browser, F4 for code execution). Powerful, but a real barrier for non-terminal users.

How to use it

Every Web UI session you open in a Launcher tab, or in a detached window through the Launcher, comes with a bundled gateway. From the connection panel (computer icon) you control five separate opt-in permissions:

- Files read

- Files write

- Code execution

- Use my Browser

- Computer Use

Computer Use and Host Browser Use no longer need a terminal at all. The gateway works with your local machine or a remote one, and a single Disconnect button revokes everything instantly.

Why it's important for Agent Zero

The agent stays sandboxed by default. Host access becomes an explicit, granular, reversible decision instead of a terminal ritual. Same security model, much lower friction.

How to update

Launcher: close and reopen the app, then click the Update button that appears on restart.

CLI: run a0 update in your terminal.

Web UI: Settings > Check for updates > Review update.

Links

Launcher release: https://github.com/agent0ai/a0-launcher/releases/tag/v1.3

Core release: https://github.com/agent0ai/agent-zero/releases/tag/v2.5

Install guide: https://www.agent-zero.ai/p/docs/installation

0:47

7 comments

Agent Zero v2.5 + Launcher: meet the Host Access Gateway