Skip to main content

Cursor

Set up Cursor with KeepKite

Fix failing chat, completions and agent requests in Cursor with TUN mode, editor proxy settings and HTTP/1.1 compatibility mode.

Updated 2026-10-11

Cursor is a desktop app built on VS Code, and some of its requests ignore terminal environment variables — so TUN mode is the easiest setup.

Step 1: Import your subscription and turn on TUN

  1. Import your KeepKite subscription as described in the Codex CLI guide.
  2. Turn on TUN mode in your client and choose rule-based routing.
  3. Quit Cursor completely (Cmd + Q on macOS, quit from the tray on Windows) and reopen it.

Step 2 (optional): System proxy only

If you can't use TUN, open Cursor's settings.json (Command Palette → Preferences: Open User Settings (JSON)) and add:

{
  "http.proxy": "http://127.0.0.1:7897",
  "http.proxySupport": "override",
  "http.noProxy": ["localhost", "127.0.0.1"]
}

Use your client's mixed port, save, and restart Cursor.

Step 3: Turn on HTTP/1.1 compatibility mode

On some networks long-lived HTTP/2 connections get interrupted, which shows up as chats hanging or the agent stopping halfway. In Cursor Settings → Network, set HTTP compatibility mode to HTTP/1.1, then click Run Diagnostic and check that every item passes.

Step 4: The Codex extension in Cursor

The OpenAI Codex extension inside Cursor also benefits from TUN mode with no extra setup. If its sign-in hangs, make sure http.noProxy includes localhost.

Verify

In Cursor's integrated terminal, run:

curl -fsSL https://app.keepkite.com/check.sh | bash

Then send a message in Chat. If the network diagnostic still shows failures, see Troubleshooting.

No subscription yet?

Sign up for KeepKite and get Codex connected in minutes.

Get started