Edgecase for Cursor: Autocompleting an old API endpoint
Posted on:
I was trying to use Cursor’s tab complete against the Todoist API for a side project, and Todoist recently (8 months ago as of writing this) merged their two /rest/v2/ and /sync/v9/ endpoints to a unified /api/v1/ endpoint. Due to such, Cursor was stepping on itself trying to figure out the endpoint. I had the docs up to the side so I found out that the old APIs were deprecated and what the new one was, but due to the tab complete being trained on the old ones / just having more examples of the old api in its training set, it didn’t know about the update by default.
I wasn't particularly frustrated with this edgecase, but it is just an example of the current state of large language models being probabalistic by nature as well as having to manage with their cutoff windows for up to date knowledge. Technically if I was using Cursor's agent mode and it went to their official docs, it may have seen that deprecation, but I didn't and ended up in this situation.