Skip to content

Cursor proxy being too slow compared to regular codex subscription #2300

Description

@Taewan-P

Client or integration

Codex App

Area

Proxy and routing

Summary

I experience a extreme slow api while using cursor as the codex proxy. This is not fast mode btw. Compared to using the cursor client, the same model feels 2~3 times more slow in Codex.

Reproduction

  1. Use cursor model as the codex backend
  2. Try using it

Version

2.28.0

Operating system

MacOS 26.5.2

Provider and model

cursor/ any model

Logs or error output

I do see some log like this:


  "requestId": "ocx-mt338y13-15",
  "timestamp": 1787325152583,
  "model": "gpt-5.6-sol",
  "provider": "cursor",
  "admissionKind": "loopback",
  "inboundProtocol": "responses",
  "conversationId": "810343447cae6ba56e96fc7a5e9a3636",
  "requestedModel": "cursor/gpt-5.6-sol",
  "requestedEffort": "max",
  "resolvedModel": "gpt-5.6-sol",
  "status": 502,
  "durationMs": 43773,
  "firstOutputMs": 8859,


As you can see, first output was 8seconds later and it was killed after 43 seconds. However, nothing was printed on the Codex side. This is extremely slow.

Screenshots and supporting files

No response

Redacted configuration

Checks

  • I searched existing issues and documentation.
  • I removed secrets, tokens, account details, request credentials, and personal data.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingproviderProvider adapters, OpenAI-compat presets, upstream API quirksproxyHTTP proxy, routing, reverse-proxy / management authstreamingSSE, WebSocket, terminal stream frames

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions