Routing AI Services Separately: Stop the IP From Hopping

Services like ChatGPT and Claude are unusually sensitive to your exit IP: change it mid-session and you get re-verification, land on a flagged datacentre range and you get a page that simply won't load. Pulling them out of the default proxy group removes most of that pain.

The point is a stable IP

Build the group with select and pin one node. Do not use url-test:

append-proxy-groups:
  - name: "AI"
    type: select
    proxies: [DIRECT]

A latency-tested group rotates between nodes, so the far end sees the IP changing repeatedly inside one session. Verification challenges are then more or less guaranteed. The differences between group types are in proxy groups.

SponsoredWhere does the subscription link come from?Our partner provider gives you 1 GB of high-speed Hong Kong data at signup — import it in one click.Get high-speed nodes

Writing the rules

It is never a single domain: sign-in, static assets and the desktop client's API often sit on separate hostnames, so a hand-written list will always miss something. Reference a maintained rule set instead — see rule providers:

prepend-rules:
  - RULE-SET,ai,AI

Symptom to cause

• Page spins forever — that node's IP is blocked by the service. Switch nodes;
• Constant re-verification — the group is still url-test and the IP keeps moving;
• Website works, desktop app doesn't — that app ignores the system proxy. Turn on TUN, see system proxy vs TUN.