Repository navigation
ma-browser v0.14.0 — slim core: faster snapshots and clicks, real multi-agent sessions
LatestSlim core line, rebuilt from v0.12.0. The v0.13.0 features (site_freeze,
adapter cache/health, dynamic MCP tools, vault, remote access) are not
included; they remain in the v0.13.0 tag.
Removed
- web control panel, Windows tray app, Pinix Hub provider, OpenClaw backend
- background
git pullafter everysitecommand and the npm version check
Features
- cli:
tab claim [--id] [--shared] [--intent]/tab releasefor exclusive tabs - cli:
snapshot --highlightdraws the numbered ref boxes on request (MCP:highlight: true) - daemon: idle sessions expire after
BB_SESSION_IDLE_HOURS(default 24) and release their leases - scripts:
e2e.mjs(core agent contract in an isolated browser) andbench.mjs
Performance
- snapshot: no overlay by default; a 400-row page went from 15.6s to 2.0s, same output
- click: focus emulation on attach; background-tab clicks went from ~10s to <1s
- daemon: cap Chrome's per-tab network body buffer (10MB/tab, 5MB/response): -155MB Chromium PSS with six API-heavy tabs
- daemon: stop enabling the unused Accessibility domain on every tab
Bug Fixes
- cli: send
BB_SESSION_ID/BB_SESSION_LABEL/BB_SESSION_SCOPE, so CLI agents get their own current tab - click: one click fires the handler once (was mouse click plus
element.click()) - tabs: hex short IDs are no longer parseInt-ed, and unknown IDs error instead of falling back to a list index
- site: one adapter catalog/runner shared by CLI, MCP and daemon;
site rungoes through the daemon's sessions and leases
Verify
node scripts/e2e.mjs # isolated Chromium + daemon: control, sessions, leases, adapters, cookie persistence
node scripts/bench.mjs # memory/latency benchmark🤖 Generated with Claude Code