Hi! Thank you for developing cli-proxy-api—it’s been super useful!
I'd like to suggest adding native proxy support for Cursor / Cursor Agent API.
Currently, models provided via Cursor CLI/API (such as cursor-grok-4.5 variants and composer-2.5) work really well. Right now, I have to run an external local wrapper and bridge it into cli-proxy-api using openai-compatibility, which feels a bit cumbersome to maintain.
It would be awesome if cli-proxy-api could support Cursor as a native provider (e.g., configuring it directly in config.yaml, routing/queuing requests, and tracking usage stats in the dashboard) without needing an extra background service.
Thanks for considering this!
Hi! Thank you for developing
cli-proxy-api—it’s been super useful!I'd like to suggest adding native proxy support for Cursor / Cursor Agent API.
Currently, models provided via Cursor CLI/API (such as
cursor-grok-4.5variants andcomposer-2.5) work really well. Right now, I have to run an external local wrapper and bridge it intocli-proxy-apiusingopenai-compatibility, which feels a bit cumbersome to maintain.It would be awesome if
cli-proxy-apicould support Cursor as a native provider (e.g., configuring it directly inconfig.yaml, routing/queuing requests, and tracking usage stats in the dashboard) without needing an extra background service.Thanks for considering this!