Vibium Files

MCP Recording Overhaul

JS/Python API and MCP/CLI recording now share the same recorder and produce identical trace output.

New MCP recording tools

Four new tools for structuring recordings:

• browser_record_start_group / browser_record_stop_group — nest actions into named groups in the trace viewer
• browser_record_start_chunk / browser_record_stop_chunk — split long recordings into separate zip files without stopping

New CLI subcommands to match:

:::bash
vibium record start-group "Login"
vibium record stop-group
vibium record start-chunk --name "part2" --title "Checkout Flow"
vibium record stop-chunk -o part1.zip

New recording options

browser_record_start now accepts title, format, quality, and sources parameters. The CLI gains --title and --sources flags.

:::bash
vibium record start --screenshots --title "Login Flow" --quality 0.1

Bug fixes

• Screenshot timing: MCP recordings now align screenshot timestamps with the action's endTime (matching the proxy path) instead of using the later capture time. This fixes timing gaps in the trace viewer.
• Missing event subscriptions: MCP recording now subscribes to log.entryAdded, browsingContext.userPromptOpened, browsingContext.downloadWillBegin, browsingContext.load, and browsingContext.fragmentNavigated — matching the proxy's event coverage.
• Element bounding boxes: Click/hover/tap actions in MCP recordings now include input events with point and box data, enabling click-dot overlays in the trace viewer.
• BiDi event forwarding: bidi.Client now supports a SetEventHandler callback so events received during command waits are forwarded to the recorder.

Full Changelog: https://github.com/VibiumDev/vibium/compare/v26.3.9...v26.3.11