Hey @Tara @ppb, quick important note: OpenRouter isn’t officially supported in Cursor. The supported BYOK providers are OpenAI, Anthropic, Google AI, Azure OpenAI, and AWS Bedrock. Using Cursor + OpenRouter via an Override OpenAI Base URL is known to be partially broken. You can hit request format errors, tools issues, and other incompatibilities. It’s an unsupported workaround, not an official path.
That’s also why Kimi K2.5 breaks. When Override OpenAI Base URL is enabled, requests go to your endpoint (OpenRouter), and models that overlap with built-in Cursor ones fail more often because of how Cursor formats requests for them. The trouble finding the resource error is from the same kind of incompatibility.
What you can do for GLM 5.2 officially:
- If your provider has a direct OpenAI-compatible endpoint (for example, a direct key from Z.ai), use it in Settings > Models with Override OpenAI Base URL. A direct provider key is usually more reliable than an aggregator.
- Or wait for first-party GLM support in Cursor. It’s a popular request and we see it regularly, but I can’t share a specific timeline.
If you try a direct endpoint and still hit an error, send the Request ID with Privacy Mode turned off and we’ll take a look.