# Claude computer use wrong country shipping

You asked Claude computer use to check a catalog or a ship-to country. The Chrome it drives sits on a cloud machine, and the shop reads that VM datacenter IP. The storefront that opens is the host's country: the wrong country catalog, a different ship-to list, or a checkout that will not send the order where you meant.

Claude computer use wrong country shipping is that mismatch. The browser egress belongs to the cloud VM, not to the country the catalog should match. Ask the agent to run setup on the host that already owns that Chrome. Aluvia does not move Claude onto another machine, and it does not change which regions the model will serve.

## The shop read the VM, not the shipping country

Claude computer use opens a real Chrome session on the cloud host. Sites pick catalog, currency, and whether they will ship to an address from that request IP. We built Aluvia as a local CLI and proxy daemon for that same Chrome.

A laptop VPN never reaches this browser. Installing next to the chat client configures a different machine. [Change a cloud browser's IP country without a VPN](/geo/without-a-vpn).

## Change the IP country of the Chrome computer use already has

Ask the agent to run `npx aluvia-cli setup` on the computer-use host. 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. Save unfinished work; the first configuration can restart Chrome.

## Install on the computer-use 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, a usable local Chrome or Chromium browser, and command access to its host. No target page URL is required. Initial configuration can restart Chrome. [Quickstart](/docs), [setup changes](/setup), [runtime evidence](/compatibility).

## Check setup before continuing

Read the JSON result. `ready: true` confirms the browser/proxy path and upstream check, not target-site access. Follow `next` if recovery is needed. Successful setup already enables proxy traffic. If `aluvia` is not on PATH, use `npx aluvia-cli` instead.

## Check country availability

Choose the country the task needs from the current list. The command below is an example; substitute an available country or skip selection if the global pool is suitable.

```sh
aluvia geos
```

## Point this Chrome at US, or the country shipping and catalog expect

Run `aluvia geos` and pick the country the catalog or ship-to list should match. `aluvia proxy-on --geo US` sends the existing computer-use Chrome through a United States residential or mobile IP when that is the country shipping expects. Replace `US` with another code from that list when the storefront named a different country.

Reload the same tab and read the catalog, the ship-to line, and the checkout country. Sticky sessions last up to 30 minutes. A saved delivery address, tax setting, or account country can still override the page.

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

## If shipping is still the VM's country

If the shop still serves the datacenter catalog or ship-to list, `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
```

## What a country IP does not fix

A residential or mobile country exit sometimes fixes an IP-based catalog or shipping country. It does not fix Claude model-region eligibility, a billing address or tax setting, a password or 2FA prompt, or a screenshot-misclick on a country dropdown. Aluvia does not claim to beat fingerprint, TLS, or canvas.

This is not a human VPN, not a streaming tool, and not an MCP. It will not complete a login. [What setup changes](/setup). The [country guide](/geo) is the place to start when you already know which country the page expects.

## Reload and verify

Reload the target using the same browser tool and check the required content. Run status and follow its `next` field. For a suspected IP refusal, rotate once and reload; stop if it still fails. For a rate limit, wait and reduce requests.

```sh
aluvia status
```

## Undo the IP change

When finished, return to the machine's IP. After setup, this keeps Chrome running.

```sh
aluvia proxy-off
```

## When the trial ends

Show the actual `claim_url` from `payment_required` to the operator. They can claim the account and buy data at 2 USD per GB. Run `aluvia auth login` to wait, inspect the response and retry. Never invent a claim URL or reveal a key. [Payment handoff](/e/payment_required).

---

Source: https://aluvia.io/geo/claude