dashboard: add --addr flag for configurable bind address

[jmjoy]

Problem

The dashboard server was hardcoded to bind to 127.0.0.1, making it impossible to run the dashboard inside a Docker container and access it from the host machine. Requests from the host
(or any external network) would be rejected since 127.0.0.1 only accepts connections from within the container's own network namespace.

Solution

Add a new --addr CLI flag to agent-browser dashboard start that allows specifying the bind address. The default remains 127.0.0.1 for full backwards compatibility.

Usage

# Default behavior (unchanged)
agent-browser dashboard start

# Bind to all interfaces (Docker-friendly)
agent-browser dashboard start --addr 0.0.0.0

# Custom port + address
agent-browser dashboard start --addr 0.0.0.0 --port 8080

Changes

• cli/src/native/stream/dashboard.rs — run_dashboard_server now accepts addr: &str instead of hardcoding 127.0.0.1:port
• cli/src/main.rs — Parses --addr from CLI args, passes it to the daemon via AGENT_BROWSER_DASHBOARD_ADDR env var
• cli/src/output.rs — Updated --help output with new flag and examples

Backwards compatibility

No breaking changes. Omitting --addr defaults to 127.0.0.1, matching the previous behavior exactly.

[vercel]

@jmjoy is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

Additional Suggestion:

The "Dashboard started" success message uses hardcoded "localhost" instead of the user-provided addr parameter, showing incorrect URL when a non-localhost address is specified.