Dashboard

Dashboard

A read-only page on your own computer that shows what your BrowserForge has installed and what it is doing.

browserforge serve               # in one terminal
browserforge dashboard           # opens http://127.0.0.1:7345/dashboard
browserforge dashboard --print   # only print the address

On Windows use the BrowserForge dashboard Start-menu entry.

Tab	Shows
Overview	Server version and uptime, connected browsers, MCP sessions, counts of tools, plugins, skills and flows
MCP	How to connect an agent; every tool grouped by area or plugin, filterable, read-only tools marked
Plugins	Loaded, skipped (and why) or switched-off plugins, what each may do in plain words, the tools it adds
Skills	Each skill, what it needs, its workflows and inputs
Flows	The 20 newest recorded flows, with steps, approvals needed, outcome, replays
Local models	Whether Qwen and Laya are reachable, and who decided how many steps and how those runs went

It refreshes every 5 seconds and changes nothing; each tab shows the terminal command for the change you may want. Switching plugins on and off from the page is planned (issue #7).

Why it is safe to leave open

Its data needs a separate dashboard token (the MCP token does not open it, and it opens nothing else); the token travels after the # in the address, which browsers never send to a server; only the page itself may call the data address; a strict Content-Security-Policy lets nothing but its own two files run; and text from plugins or skills is shown as plain text, never as HTML. Details: docs/DASHBOARD.md · docs/SECURITY.md.