proxy_server to "self", Smooth creates a peer-to-peer tunnel between the remote Smooth browser and your local machine, routing all browser traffic through your network. This is useful for:
- Accessing localhost — The tunnel lets the Smooth browser reach services running on your machine (e.g.
http://localhost:3000), making it easy to test local development environments - Avoiding bot detection — Many websites trust residential IPs more than datacenter IPs
- Geo-localized automations — Access location-specific content based on your actual location
- Location-aware queries — Run searches like “restaurants near me” that rely on IP geolocation
- Accessing region-restricted content — Browse content only available in your region
Usage
Accessing Localhost
Because the P2P tunnel connects the Smooth browser directly to your machine, the browser can reach any service running locally — just uselocalhost or 127.0.0.1 as you normally would:
With Sessions
How It Works
When you setproxy_server="self":
- Smooth establishes a peer-to-peer tunnel between the remote browser and your machine
- All browser traffic is routed through your local network
- Websites see your IP address instead of Smooth’s datacenter IP
- Services running on
localhostbecome reachable from the Smooth browser - The tunnel is automatically closed when the task or session ends
This feature is most useful when running automations from a local machine with a residential IP. If your code is running from a datacenter, the tunnel will still use a datacenter IP.