Expand description
Lazy shared Chromium instance used by the browser MCP tools.
The browser is launched on first use and kept alive for the lifetime of the
Boost server process. We hold its Handler future in a detached background
task so DevTools events keep flowing while we drive pages from the tools.
Failure mode: if Chromium isn’t installed and chromiumoxide can’t find one
on PATH, every call returns a clean MCP error explaining how to fix it.
Tools never panic.