Cursor / Windsurf：接入边界
Cursor documents BYOK under Cursor Settings → Models → provider API key. That does not establish arbitrary third-party endpoints in every release or BYOK support for Tab completion. Only if your actual UI offers a custom/Override OpenAI Base URL should you enter https://api.nekocloud.vip/v1, your NekoCloud key and a protocol-compatible model. Without that control, do not submit a NekoCloud key to an official-only verification form or patch the client.
Cursor says requests use its backend for final prompt construction and the key is transmitted with requests. This is not purely local direct access and its zero-retention policy does not apply to BYOK.
Windsurf BYOK depends on version, account and supported providers; a general custom endpoint is not confirmed here. For an explicit third-party API workflow, consider Cline, Kilo, Continue or OpenCode.
Verification and safety
Back up existing settings and merge only relevant fields; preserve other providers, plugins, MCP and permissions. Protect keys and backups, never commit them. Variables must reach the actual agent process; Remote SSH, containers and desktop processes have separate environments.
Relaunch, select the NekoCloud model, send a short message and match time, model and charge in Usage. Then read a non-sensitive file in an isolated project and verify the tool call, returned result and final answer. Tests can incur charges. Keep approval controls enabled.
This is adapted from official provider configuration guidance, not proof that every model or the complete NekoCloud tool chain has been tested. Check Model Plaza, key groups and troubleshooting.