Knowledge base · TOPIC-08

Cursor website works, but the client does not

Short answer: loading cursor.com proves one browser path. Cursor documents separate client connections, proxy behavior, and streaming requirements, so a successful page load does not establish that the desktop workflow is healthy.

Separate observations from causes

A browser and a native client may use different destinations, certificate stores, proxy inheritance, and connection lifetimes. Cursor’s documentation says its network diagnostics can test service connections and notes that some proxies interfere with HTTP/2 streaming. Those are provider-reported possibilities—not proof that a particular proxy caused your incident.

Record the client error and time, then check DNS, TCP, and certificate-validated TLS before changing settings. Compare one trusted alternate network and consult Cursor’s own diagnostics. Do not copy cookies, tokens, or proxy credentials into a report.

Tivor Open Probe V0.1 does not support a Cursor provider-path adapter, inspect the Cursor process, diagnose proxy/PAC inheritance, or measure HTTP/2 streaming. It can still provide local network context, but Cursor remains UNSUPPORTED / NOT_EXECUTED in V0.1. Use the browser Scanner for a bounded web view and Open Probe for local evidence; preserve uncertainty when evidence is incomplete.

Related: Why the browser can work while an AI agent fails.