App Proxy

Set Up a Proxy for Cursor AI in Clash Verge: Fix Chat and Completion Timeouts

Cursor chat/completion/agent traffic hits overseas services. Browser works, Cursor times out—usually the editor isn’t proxied. Prefer Tun; otherwise set HTTP proxy inside Cursor.

Overview: Tun & AI; Tun failures: start failed.

Tun or in-app proxy

PathBest whenWatch for
TunDaily use, want one switchEnable, restart Cursor, watch connections
In-app proxyTun blocked by policyWrong port, DIRECT rules, system-proxy myths

Tun: enable, restart Cursor, watch connections.

In-app: 127.0.0.1 + mixed port (ports). Still unused: wrong port, DIRECT rules (routing), or system proxy myths (system proxy).

Acceptance

  1. One short chat/completion with connection hits.
  2. Separate login vs completion failures.
  3. Slow/drops: nodes/peak (latency, slow speed).

DIRECT overreach

Broad DIRECT patches can hit API hosts—tighten (DIRECT rules). CLI issues belong in Claude/Codex posts.

Stop

Don’t stack Tun + in-app without verifying. Region issues: ChatGPT. Builds: download center.

Get a stable proxy before using Cursor

Cursor's AI features need a proxy to reach overseas services. Get Clash Verge Rev from the download center, then configure the proxy for Cursor below.