Hey, this is a known issue with Clash proxy. When --proxy-server routes all traffic through it, TLS to api2.cursor.sh breaks.
Two options to fix it.
Option 1, Clash Verge rules, recommended.
Add these to your Clash Verge merge config so Cursor domains go direct:
prepend-rules:
- 'DOMAIN-SUFFIX,cursor.sh,DIRECT'
- 'DOMAIN-SUFFIX,cursor-cdn.com,DIRECT'
- 'DOMAIN-SUFFIX,cursorapi.com,DIRECT'
- 'DOMAIN-SUFFIX,downloads.cursor.com,DIRECT'
- 'DOMAIN-SUFFIX,todesktop.com,DIRECT'
Option 2, Chromium bypass flag.
/Applications/Cursor.app/Contents/MacOS/Cursor \
--proxy-server=http://127.0.0.1:7892 \
--proxy-bypass-list="*.cursor.sh;*.cursor-cdn.com;*.cursorapi.com;*.cursor.com;*.todesktop.com"
Also add this to your Cursor settings.json to avoid HTTP/2 streaming issues through the proxy:
{
"cursor.general.disableHttp2": true
}
More details and discussion from other Clash users here: Can not use cursor because of clash verge
Let me know if it helps.