blog(cursor): route Cursor through LiteLLM - #824
Open
mateo-berri wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
New blog post at
blog/cursor_integration/, slugcursor-integration, announcing the Cursor integration end to end: the BYOK setup against<proxy>/cursorfrom the tutorial, the/cursor/chat/completionsdialect handling that makes agent mode work (original integration in BerriAI/litellm#17855), thinking/fast model variant resolution (BerriAI/litellm#35554) with per-model budgets binding to the resolved variant (BerriAI/litellm#35834), the Cursor Cloud Agents passthrough (BerriAI/litellm#34029), and the MCP path from the tutorial. Availability is stated as v1.97.0 since the Cloud Agents and variant work is tagged in the v1.97.0 dev lineIncludes an SVG flow diagram of the two traffic paths through the gateway, drawn with an opaque light background so it stays readable in dark mode
npm run buildpasses; the remaining warnings are pre-existing and none reference the new post