2 min lesson
Network realities in regulated environments
Choose two examples from the table in "Network realities in regulated environments" and explain what each teaches you to do.
Step 1 of 2
Network realities in regulated environments
Cursor's AI features need to reach Anysphere's services. In corporate networks that path runs through a proxy or firewall and air-gapped or heavily regulated environments may block it entirely. When AI features fail but the editor works, suspect the network before the product.
- Network condition
- Corporate proxy
- Typical symptom
- Requests time out or fail with TLS errors
- Where to point
- Proxy allowlist and proxy settings in the editor/OS
- Network condition
- Firewall / allowlist
- Typical symptom
- AI features dead, editor fine
- Where to point
- Required Cursor/Anysphere endpoints not allowlisted
- Network condition
- Air-gapped / regulated
- Typical symptom
- No outbound AI calls possible
- Where to point
- Deployment options and admin discussion; not a client bug
| Network condition | Typical symptom | Where to point |
|---|---|---|
| Corporate proxy | Requests time out or fail with TLS errors | Proxy allowlist and proxy settings in the editor/OS |
| Firewall / allowlist | AI features dead, editor fine | Required Cursor/Anysphere endpoints not allowlisted |
| Air-gapped / regulated | No outbound AI calls possible | Deployment options and admin discussion; not a client bug |
Editor works but AI doesn't is the classic network-not-product signature.
In the cross-functional round, show you triage the type of issue, not just the issue: "This is a config question, so I route it to the admin and our docs; this one reproduces on a clean network, so it's a real bug and I write the repro for Eng."
Demonstrating that you protect Engineering's time by filtering confusion from defects is exactly the support-scaling instinct Cursor hires for.
"Good news - the editor itself is healthy, the AI calls are being blocked before they leave your network. That points at the proxy or firewall rather than Cursor. Can you confirm with your IT admin that our endpoints are allowlisted? I'll send the exact list so the change is quick."