# change cloud agent browser country without a VPN

You handed a storefront to a cloud agent. The tab that opened is Chrome on that agent's machine, and the country it presents is the VM's. Pages that explain how to change cloud agent browser geo country without VPN usually start from a laptop you sit at. That laptop is not this browser.

To change cloud agent browser country without a VPN, the country exit has to land on the host that already runs Chrome. A VPN on your laptop never reaches that process. Chrome DevTools Sensors rewrite a location hint on a desktop you control; they do not change the request IP of a browser already in a datacenter. A hosted cloud-browser API that accepts country= on a WebSocket opens a different Chrome than the one the agent already has. To change cloud Chrome geo without VPN software on your laptop, leave the agent where it is and give that existing browser a residential or mobile IP in the country the catalog should match.

## The shop already chose the VM's country

Most sites pick language, prices, and whether a page even exists from the request IP. Cloud Chrome leaves a datacenter address, so a job that named one country can still receive another. You end up comparing the VM's catalog instead of the one you asked for.

If the agent is [Cursor](/geo/cursor), setup belongs on the cloud host that owns Chrome, not next to the editor. The [country guide](/geo) is the place to start when you already know which country the page expects.

## Attach a country exit to the Chrome the agent already has

We built Aluvia as a local CLI and proxy daemon for that existing browser. Ask the agent to run `npx aluvia-cli setup` there. First 10 MB free without an account, API key, or payment; then 2 USD per GB. Country only: Aluvia does not pick a city and does not write GPS, timezone, or Accept-Language. This is not a human VPN and not an MCP.

## Set up on the agent's browser host

```sh
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](/docs), [runtime evidence](/compatibility).

## Choose the country the catalog needs

Run `aluvia geos` and pick an available country. `aluvia proxy-on --geo US` is the example when the page expects the United States; substitute the country the catalog, prices, or language should match. Reload the same tab. Sticky sessions last up to 30 minutes. A saved account country or shipping address can still override the page.

```sh
aluvia geos
aluvia proxy-on --geo US
```

## One other address in the same country

If the storefront is still the VM's catalog, `aluvia rotate-ip` requests one different residential or mobile IP in the country you already selected. It does not change country. Try once, then stop.

```sh
aluvia rotate-ip
```

## Hand the browser back to the VM address

When the regional check is finished, `aluvia proxy-off` returns Chrome to the machine's own IP. After setup, the browser keeps running; tabs and cookies stay. [What setup changes](/setup).

```sh
aluvia proxy-off
```

## What a country IP does not change

A residential or mobile IP in the right country sometimes helps a 403 or a challenge page. That is not a promise. Aluvia does not beat fingerprint, TLS, or canvas, and it does not complete a login.

## When the trial allowance is spent

The first 10 MB does not need an account or an API key. When a command that needs the network returns `payment_required`, show the operator the actual `claim_url` from the CLI. They claim the account and buy data at 2 USD per GB; the agent runs `aluvia auth login` and waits. [Payment handoff](/e/payment_required).

---

Source: https://aluvia.io/geo/without-a-vpn