RIXNO / 2026.10.15

How I configured my Claude environment

Browser profiles, CLI settings and network checks

Claude is running. Here are the browser and CLI settings I currently use. Specific exits and account details are omitted; adapt the setup to your own environment.

A separate Chrome profile

Create a profile from Chrome's avatar menu, then configure extensions in that window. I keep Claude login state and extensions there. Profiles separate cookies, history and extension configuration, but do not create separate computers.

In ZeroOmega, create a proxy profile, select HTTP or SOCKS5 to match the local proxy client, and enter the loopback host and the client's listening port. Select that mode in the extension menu. This sets a local entry point; the client node and routing determine the exit.

Check the observed exit from inside that browser profile. Other Chrome profiles need their own configuration checks. A saved proxy address does not prove which mode is currently selected.

WebRTC, location and language

WebRTC Control is installed. The saved Chrome policy WebRtcIPHandlingPolicy=disable_non_proxied_udp restricts WebRTC UDP that does not pass through a proxy. Check extension activation and inspect chrome://policy to see whether Chrome loaded the policy, then examine candidate addresses in a WebRTC test.

System location permission is disabled. Browser location permissions and individual site grants can be inspected at chrome://settings/content/location. Location APIs and HTTP exit IP checks measure different things.

The browser language list contains English and Chinese; the system region has also been configured. Language, region and timezone settings do not change the network exit. A scanner score is not an account-safety guarantee.

The CLI needs its own proxy settings

CLAUDE_CONFIG_DIR points to a separate directory for configuration and login state. Networking is configured separately.

The launch environment sets HTTP_PROXY, HTTPS_PROXY and ALL_PROXY, including lowercase variants. NO_PROXY excludes loopback hosts. NODE_USE_ENV_PROXY=1 is set for Node versions that support environment proxies.

Pass these settings to the process launching the CLI through a wrapper or dedicated terminal environment, using your own local proxy entry. ZeroOmega settings do not automatically reach terminal processes. Claude Desktop, WSL and independently launched MCP tools need separate checks.

What the checks tell me

An exit-IP check shows where a particular request leaves the network. A DNS test identifies observed resolvers. A WebRTC test shows candidate addresses exposed by the browser. Passing one does not verify the others; private addresses alone do not establish a public-IP leak.

Earlier curl, Python urllib and Node fetch tests returned the same exit. This review only read saved settings. No browser modes were switched, active pages refreshed or Claude requests sent. Saved configuration, current browser state and observed request paths are separate evidence.

Third-party tools may ignore proxy variables, and profiles do not prevent server-side account correlation. This setup is not a guarantee against suspension.

Availability updates

2026-10-15 08:40 UTC: Claude confirmed running. This is the start of the log. Environment changes and issues will be added as reported.