Cursor setup

Route Cursor through aiproxy so every AI request the editor issues stays visible. Cursor includes an embedded agent that talks to Codex/Copilot APIs through their proprietary GRPX endpoint. Putting aiproxy in the middle lets you log, audit, or mutate each call without modifying individual integrations.

• aiproxy running locally (examples use http://localhost:8080)
• Install the aiproxy certificate authority (see Quick Start → TLS certificate)
• Cursor version 0.45 or newer

Cursor defaults to HTTP/2 networking, which many forward proxies cannot handle. Switch to HTTP/1.1 for proxy support:

1. Open Cursor Settings (⇧⌘J or Ctrl+Shift+J).
2. Select the Network tab.
3. Enable HTTP Compatibility Mode and choose HTTP/1.1.

Restart Cursor after toggling the setting.

Cursor inherits the VS Code networking stack. Update the built-in VS Code settings to use aiproxy:

1. Press ⌘, (macOS) or Ctrl+, (Windows/Linux) to open Settings.
2. Search for Proxy.
3. Under Application → Proxy, set the value to http://localhost:8080.

If you run Cursor via Flatpak or another sandbox, ensure the sandbox trusts the aiproxy certificate authority as outlined in the VS Code Copilot guide.

Run a simple request from Cursor—for example, open the command palette and ask the agent to summarize the current file. Watch the aiproxy logs or terminal UI for traffic hitting /v1/ endpoints. If you do not see traffic:

• Confirm HTTP compatibility mode remains on
• Ensure the proxy value still points at http://localhost:8080
• Verify the certificate authority appears in your OS trust store