it continues to happen for us as well
@yxap’s issue was resolved, @Roman_Mozil’s is still an open issue!
It’s not possible to know which issue you’re facing (or not) without a Request ID.
I’m referring to @Roman_Mozil’s issue: the normalization of the model name from databricks-claude-opus-4-7 to claude-opus-4-7 causing the model not to be recognized by AI Gateway.
Is there a better way for us to track this issue? Would you like us to create a new ticket/post?
Posting here is fine! And, I can confirm the bug is still open on our side.
@Colin thanks for the update. Any idea on an ETA for resolution?
For any other posters encountering this: a workaround is to create a new AI Gateway endpoint called claude-opus-4-7 in the Databricks workspace you have connected to Cursor.
Since Cursor is rewriting the model name databricks-claude-opus-4-7to claude-opus-4-7, creating a model called claude-opus-4-7 will resolve the resource not found error.
A word of caution: ensure you have actually selected system.ai.databricks-claude-opus-4-7 as the underlying model. As a custom endpoint, it’s name and underlying model can be anything!