This article examines Muse's browser capabilities by analyzing its filesystem and architecture. The system uses a separate pool of pre-warmed VMs running Chromium controlled by a Rust broker, with traffic routed through residential IPs via Oxylabs to avoid website blocking and detection. The setup prioritizes latency and task completion by separating browser execution from the agent's VM and providing datacenter-to-residential IP routing.
This article examines Muse's browser infrastructure, revealing that it uses a near-stock Chromium installation controlled by a Rust broker that manages a pool of pre-warmed VMs. The system routes browser traffic through residential internet access via Oxylabs to avoid detection and blocking by websites that restrict datacenter IPs.