You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Dashboard: allow binding to 0.0.0.0 (or add a --host flag) so it works from Docker
#2317
Right now the dashboard only binds to 127.0.0.1 and [::1] (run_dashboard_server in cli/src/native/stream/dashboard.rs). That makes it annoying to use inside a Docker container. Publishing the port with -p 4848:4848 doesn't help, because Docker forwards traffic to the container's network interface, not its loopback, so localhost:4848 on the host never reaches the dashboard.
What I'd like is to run agent-browser in a container, publish the port, and open http://localhost:4848 on my host. Next.js dev does this by default.
Options:
Bind to 0.0.0.0 / :: by default, like next dev.
Or keep loopback as the default and add --host <addr> (plus something like AGENT_BROWSER_DASHBOARD_HOST), so I can run agent-browser dashboard start --host 0.0.0.0.
I get why loopback is the safe default, so option 2 is totally fine. Right now the only way around it is a socat or nginx sidecar inside the container, which feels like overkill for a dev tool.
This discussion was converted from issue #2169 on November 03, 2026 06:48.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Right now the dashboard only binds to
127.0.0.1and[::1](run_dashboard_serverincli/src/native/stream/dashboard.rs). That makes it annoying to use inside a Docker container. Publishing the port with-p 4848:4848doesn't help, because Docker forwards traffic to the container's network interface, not its loopback, solocalhost:4848on the host never reaches the dashboard.What I'd like is to run agent-browser in a container, publish the port, and open
http://localhost:4848on my host. Next.js dev does this by default.Options:
0.0.0.0/::by default, likenext dev.--host <addr>(plus something likeAGENT_BROWSER_DASHBOARD_HOST), so I can runagent-browser dashboard start --host 0.0.0.0.I get why loopback is the safe default, so option 2 is totally fine. Right now the only way around it is a socat or nginx sidecar inside the container, which feels like overkill for a dev tool.
Thanks!
All reactions