Automated scraping
Build up a scraping workspace one worker at a time. Give each worker its own profile and connection, then watch the pages as they scroll, read, and follow links.
Video transcript
Automated scraping.
Switch to the scraping workspace and open its background profile. Configure and test a proxy. New worker panes use this connection; existing panes keep theirs.
Start one mobile worker, scrolling and reading the page. Add a second profile and device while the first keeps running. Expand to four workers, each with its own connection and commands.
Start with a profile and connection
Create a background profile for the worker. In its Connection tab, choose HTTP, HTTPS, or SOCKS5, enter the endpoint, and test the connection. Save it for new panes. Existing panes retain the connection they were created with.
Configure and test a proxyApply the worker’s device
Choose a mobile preset before opening the worker page. The visible phone frame makes its viewport easy to recognize. Keep device presentation and proxy routing configured separately for each workflow.
Simulate mobile devicesScroll, read, and follow links
Use small scroll steps, pauses, DOM reads, and clicks to work through real pages. bmux’s automation guard shares pacing and pauses across a profile’s panes. Inspect what the worker sees and extract just the content your task needs.
Browser actions and pacingExpand from one worker to four
Start one pane, add a second profile, then split the workspace as more workers begin. Each profile keeps its own logins and settings. Existing workers can continue while you add and monitor the next one.
Agent control and monitoringWatch in the web or local bmux
Run browser hosts on Linux and connect through the web viewer or the desktop Remote sessions picker. The hosting guide covers persistent storage, service access, and taking control of a remote session.
Portable hosting and remote accessInstall on macOS
Get the latest Apple Silicon or Intel release with Homebrew
brew install --cask tonisives/tap/bmuxThe bundled CLI requires Node.js 22.12 or newer.
View release notes