# Change a Cursor cloud browser's IP country

A local editor and a cloud agent can use different machines. For a regional browser task, the IP that matters is the one used by the browser making the request.

## Local and cloud tasks need different setup locations

Use the agent's shell to run setup on the machine hosting Chrome. Installing on your laptop does not change a cloud agent's browser. If the browser runs on a separate service you cannot configure, this setup path does not apply.

## Start with setup

```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
```

## Check the active browser

Choose the country after setup, then reload the tab used by the task. Do not assume that an editor window, model request, or separate browser process uses the same proxy.

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

## Limits

Aluvia changes the configured browser's IP; it does not add a country picker to Cursor or change model routing. For a [Vercel Security Checkpoint](/unblock/vercel-security-checkpoint), changing IP is a test, not a guarantee.

## 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/cursor