# OpenAI Codex browses from the cloud machine

OpenAI Codex running as a cloud agent is seen as the VM's country. Send its traffic through a residential or mobile IP in the country you set so the site returns that country's page.

Codex on a cloud machine opens URLs from that host. The site is not looking at the operator's laptop, and it is not looking at Cursor. A regional catalog or a not-available-in-your-region page is the datacenter IP.

## The command

```sh
npx aluvia-cli setup
aluvia geos
aluvia proxy-on --geo US
```

Replace `US` with the country the page should serve. Country only, not city. Sticky sessions last up to 30 minutes.

## The problem

The operator asked Codex to load a country's storefront, a ship-to check, or a page that refuses some regions. Codex can follow the link. The country those requests appear to come from is still the VM. That is the miss.

## The solution

Run `npx aluvia-cli setup` on the Codex cloud machine, then `aluvia proxy-on --geo US`. Replace `US` with the country the page should serve. Traffic then leaves through a residential or mobile IP there. `aluvia geos` lists countries. Omit `--geo` for the global pool. Sticky sessions last up to 30 minutes.

## What this does not do

This page is for OpenAI Codex as a cloud agent, not Cursor and not Grok Bot. Aluvia does not change OpenAI's model availability. It does not write GPS, timezone, or Accept-Language, will not play a stream, and will not pass a login wall. Country only, not city.

---

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