Hey, thanks for the report. There are two separate issues here, and we’re aware of both:
- kimi-k2.5 gets blocked as already available
Cursor compares your custom model name against the built-in model catalog, and kimi-k2.5 matches our built-in version. As a workaround, try adding the model with a slightly different name, like kimi-k2.5-custom or my-kimi-k2.5. If your endpoint handles that name correctly, or ignores it and uses the default model, this should work.
- glm-5-fp8 and minimax-m2.5 show Model name is not valid
This is server-side validation rejecting model names that aren’t in Cursor’s catalog. The same issue is discussed here:
Unfortunately, there isn’t a working workaround for the second issue right now. I’ll pass this to the team. Since the earlier reports, it’s still happening, and your report helps raise the priority.
Let me know if the kimi-k2.5 workaround works for you.