Hey, thanks for the continued interest in GLM 5.2. We get the request for first-party support as a built-in model a lot, but I can’t share a specific timeline yet. I’ll keep this thread open, and I’ll post an update if I have one.
@usman724 about why BYOK GLM 5.2 isn’t working: this is a known bug on our side, not an issue with your key or config. Right now the name glm-5.2 matches a model in our catalog, so your custom model gets resolved as managed, and Cursor sends the provider a modified id glm-5.2-high instead of exactly glm-5.2. The provider doesn’t recognize it and returns an error that Cursor shows as Unauthorized User API key or Model name is not valid.
There isn’t a clean client-side workaround right now. The provider needs exactly glm-5.2, but Cursor intercepts it. Until we ship a server fix, please use another model from the same provider, for example kimi-k2.7-code. I’ve reported the issue internally, no ETA yet.
For details and updates on this specific bug, it’s best to track it in a separate thread: Cursor Native Agent fails with glm-5.2 via OpenAI-compatible provider, while other agents work so it doesn’t get mixed with the feature request discussion here.
Also, about OpenRouter for anyone trying it: it’s not officially supported. Supported BYOK providers are OpenAI, Anthropic, Google AI, Azure OpenAI, AWS Bedrock. If you’re using a direct OpenAI-compatible endpoint, for example a Z.ai key, and you still hit an error, send the Request ID with Privacy Mode off and we’ll take a look.