Change a cloud agent's IP location

This page as markdown: https://aluvia.io/geo.md

Updated 2026-09-09 · Aluvia

A website can use the request IP to choose prices, a catalog, or a regional page. When your agent runs in the cloud, that IP belongs to the datacenter, which may be in a different country from the one your task needs.

Aluvia routes the existing Chrome browser through a residential IP in the country you select. Reload the page to check the result; some sites also use account settings or saved preferences.

Set up on the browser's machine

npx aluvia-cli setup

First 10 MB free without an account, API key or payment; then 2 USD per GB. Requires Node.js 18 or later and a usable local Chrome or Chromium browser on this machine. Initial configuration can restart Chrome. No target page URL is required. Inspect the JSON result and follow next before selecting a country; readiness does not prove target access. Quickstart, runtime evidence.

Choose a country

Replace US with a country from aluvia geos, then reload the target page. Omit --geo to use the global pool. Sticky sessions last up to 30 minutes.

aluvia geos
aluvia proxy-on --geo US

Agents and browser automation

• Grok Bot — a browser task on a cloud machine
• Codex — check where the browser runs
• Cursor — local versus cloud-agent browsing
• Claude computer use — wrong country shipping from a cloud VM
• OpenClaw — browser and VPS placement
• Hermes — website region versus model availability
• Muse — Muse Secure VM browser and datacenter exit
• Playwright — Playwright Chrome on the wrong regional site

IP country is not browser location

Aluvia changes the IP used by the browser. It does not change GPS, timezone, or Accept-Language, and it does not select a city. A website may also keep a country choice in a cookie or account setting.

A VPN on your laptop does not change a separate cloud browser's connection. Change a cloud browser's IP country without a VPN.

If the page is still blocked

Check the selected country and reload before trying another IP. For an IP-related refusal, try one rotation. If it still fails, stop and use the blocked-page guides. Browser checks, login requirements, and access rights can still apply.

To return to the machine's IP, run aluvia proxy-off. After setup this keeps Chrome running with its tabs and cookies. Setup details and undo steps.

Trial, undo and continuation

Reload the page and check its content, then run aluvia status. For an IP-related refusal, rotate once and stop if it still fails. Use aluvia proxy-off to return to the machine's IP without restarting Chrome after setup.

When payment_required appears, show the actual claim_url to the operator. They choose whether to buy data; the agent runs aluvia auth login to wait. Payment handoff.