Skip to main content
Start the application inside your machine before setting up sandbox port forwarding. Keep the CLI process running for as long as you need access.

​
Open an application

Start your application on an explicit guest port, then run:
The CLI opens your browser and keeps forwarding until you press Ctrl-C. It supplies bead traffic authentication. Your application’s own login still applies.

​
Forward without opening a browser

Open the printed localhost URL. Choose another local port if port 3000 is occupied. The listener binds to loopback on your computer. Keep the CLI process running while you use the application. Ctrl-C closes active forwarding, including WebSocket connections.

​
Use from an agent

bead:sandbox_open returns the machine application hostname and the local CLI command. Run that command on the computer where you want to open the application. Hosted MCP does not launch a browser on its server. Read application URLs for the hostname’s access model, raw ports for TCP or UDP services, and worktree services for declared development commands.