---
title: "Cursor: which domains it uses on a Mac, HTTP/2 and proxies, and whether to block it · Kilobat"
url: "https://kilobat.app/processes/cursor"
description: "Cursor sends AI requests to *.cursor.sh over HTTP/2 streaming. The domains, proxy rules and diagnostics Cursor documents, and what breaks if blocked."
---

# What is Cursor?

Cursor is a code editor with AI features. Its AI requests go to Cursor's servers, not to your remote host. Cursor documents the domains and proxy settings that it needs.

**Fix this with your agent**Copies a prompt for Claude Code, Codex or any agent that can use Terminal.

I want to know what Cursor is doing on my Mac and whether its network use is normal. Read https://kilobat.app/processes/cursor.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.

Process: `Cursor` · Also seen as: `Cursor Helper`, `Cursor Helper (Renderer)`, `Cursor Helper (GPU)` · Made by Anysphere · Applies to: Cursor on macOS 14 Sonoma and later. Checked on 8 November 2026 against Cursor's documentation. · Checked: 8 November 2026

## Short answer

The Cursor code editor. AI features go to *.cursor.sh over HTTP/2 streaming. Cursor documents the domains, proxy needs and a diagnostics tool.

Block with care

Blocking Cursor's domains stops its AI features, sign-in and updates. The editor opens, but it is far less useful.

Path

`/Applications/Cursor.app/Contents/MacOS/Cursor`

Signing identifier

`com.todesktop.230313mzl4w4u92`

## What it is

Cursor's network configuration page tells you to allow domain patterns, not IP addresses. The patterns are `*.cursor.sh`, `*.cursor-cdn.com`, `*.cursorapi.com` and `*.cursorvm.com`.

For firewalls that need single hosts, Cursor lists `api2.cursor.sh` for most API requests and `api5.cursor.sh` for agent requests. It lists `api3.cursor.sh` for Cursor Tab and `repo42.cursor.sh` for codebase search. Both need HTTP/2.

Updates and extensions come from `marketplace.cursorapi.com`, `cursor-cdn.com`, `downloads.cursor.com` and an Amazon S3 bucket host that Cursor names.

Authentication uses `authenticate.cursor.sh`, `authenticator.cursor.sh` and hosts that Cursor documents in a separate sign-in article.

Cursor says that it uses HTTP/2 bidirectional streaming by default. If that fails, it falls back to HTTP/1.1 Server-Sent Events.

Cursor says that SSL inspection and DLP often cause timeouts, slowness or errors with its Agent features. It recommends that you disable SSL inspection for its domains.

Cursor says that TLS 1.2 or higher is used for all connections to its services.

## Why it uses the network

- **AI requests.** Chat, agent and completion requests go to the Cursor API hosts, such as `api2.cursor.sh`.
- **Cursor Tab and codebase search.** Cursor lists separate hosts for Tab requests and codebase search. They need HTTP/2.
- **Sign-in.** Cursor lists authentication hosts for the sign-in page and token issuers.
- **Updates and extensions.** Client updates and extension downloads use the marketplace and download hosts.

## How much is normal

Cursor does not publish figures for traffic. Expect frequent small requests while you type, because Tab suggestions use the network.

Chat and agent sessions stream responses over long-lived connections.

Cursor says that when you use Remote SSH, AI requests go from your local machine to Cursor's servers.

## When it uses a lot, and why

- **Agent sessions.** Long agent runs stream a lot of data over open connections.
- **A proxy that buffers streams.** Cursor says that most connectivity problems come from proxies that buffer streaming responses.
- **Updates and extensions.** A new version or a large extension downloads in full.

## Is it safe to block?

Block with care

Blocking Cursor's domains stops its AI features, sign-in and updates. The editor opens, but it is far less useful.

What breaks if you block it

- Chat, agent and Tab features stop working.
- Sign-in fails when the authentication hosts are blocked.
- Updates and extension downloads fail.
- A proxy that blocks HTTP/2 breaks streaming unless you switch to HTTP/1.1.

Blocking means a firewall rule that refuses its connections. Don’t quit or disable a macOS process to save data: macOS starts it again, and other features depend on it.

## Reduce its use

1. Open Cursor Settings › Network and click Run Diagnostics to test your connection to Cursor's servers.
2. If a proxy blocks HTTP/2, set HTTP Compatibility Mode to HTTP/1.1 in Cursor Settings › Network. Restart Cursor.
3. On a company network, ask the administrator to exclude Cursor's domains from SSL inspection.

## See how much it uses

1. Open Activity Monitor and search for Cursor. Open the Network tab to see which Cursor processes moved data.

## With Kilobat

1. In the Kilobat app list, search for `Cursor`. Its helper processes group under the app.
2. Ask the same question in Terminal.

   ```
   kilobat explain Cursor
   ```

The live view and the explanations are free. History in the app needs Kilobat Pro. Blocking needs Pro and the network filter: see the [network filter](https://kilobat.app/docs/blocking#filtering), [Protection](https://kilobat.app/docs/blocking#protection) and the [hotspot data saver](https://kilobat.app/save-hotspot-data).

## What isn’t documented

Cursor's page does not say how much data each feature uses. It does not name the macOS helper processes.

Cursor says that its domain list may need hosts that its separate sign-in article lists. This page does not repeat that list.

Cursor does not publish how often the editor contacts its servers when you are idle.

## Questions

**Why does Cursor stall behind a proxy?**

Cursor says that it uses HTTP/2 bidirectional streaming. Some proxies, such as Zscaler, do not support it. Set HTTP Compatibility Mode to HTTP/1.1.

**How do I test Cursor's connection?**

Open Cursor Settings › Network and click Run Diagnostics. Cursor also gives curl commands in its network configuration page.

## Sources

- [Cursor Docs: Network configuration](https://cursor.com/docs/enterprise/network-configuration)
- [Cursor Help: Network, proxy, and remote connections](https://cursor.com/help/troubleshooting/network)
- [Kilobat docs: Connections](https://kilobat.app/docs)

Checked on 8 November 2026.

## Related

- [Electron Helper](https://kilobat.app/processes/electron-helpers): Part of an app built on Electron. Electron apps run their windows and their network work in helper processes, so the app's traffic shows under “App Helper”.
- [Code Helper](https://kilobat.app/processes/vscode): Visual Studio Code and its helper processes. They contact Microsoft's update, extension marketplace and sync servers, and whatever your extensions and terminals reach.
