Tools
Cursor
Connection limitations, supported alternatives and a repository audit prompt.
Supported alternatives
Cursor does not currently expose the custom endpoint setting this connection needs. Choose Zed, Continue or VS Code to connect your editor.
Limitations
- We are not listing a workaround we cannot support. If Cursor adds a base URL setting, this page changes the same day.
- For the same job with a real editor surface, see the Zed, VS Code and Continue pages.
Repository audit
This prompt audits your repository. It does not configure a Cognitivers connection.
Open repository audit prompt
Cursor cannot use a third-party endpoint: its own documentation lists five providers that accept your own key and documents no base URL field. Do not spend time trying to make it work.
Two things I do want from you, in the repository I am working in.
1. Search the code for every place this project calls an OpenAI-compatible API (the OpenAI SDKs, the Vercel AI SDK, LangChain, LiteLLM, fetch against a /v1 path) and list the file and line of each one. I want to know what would have to change if a tool did support it.
2. Check whether any of those call sites is Cursor-specific, for example an .cursor/rules file or a Cursor model name in a config, and tell me what it pins.
Do not change any file. Report what you found, and if you find nothing, say that in one line.