Development environment setup

[ishaan-jaff]

Relevant issues

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - see details
• My PR passes all unit tests on make test-unit
• My PR's scope is as isolated as possible, it only solves 1 specific problem
• I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

CI (LiteLLM team)

CI status guideline:

• 50-55 passing tests: main is stable with minor issues.
• 45-49 passing tests: acceptable but needs attention
• <= 40 passing tests: unstable; be careful with your merges and assess the risk.

• Branch creation CI run
  Link:

• CI run for the last commit
  Link:

• Merge / cherry-pick CI run
  Links:

Type

🆕 New Feature
📖 Documentation

Changes

This PR introduces native pass-through support for Cursor Cloud Agents, allowing users to manage Cursor agents via the LiteLLM proxy.

Key Changes:

• Cursor Provider Integration: Added CURSOR to LlmProviders enum and implemented a dedicated pass-through route (/cursor/{endpoint:path}) with Basic Authentication. This enables direct forwarding of requests to the Cursor Cloud Agents API.
• Enhanced Logging: Developed a CursorPassthroughLoggingHandler to accurately classify and log Cursor API operations (e.g., cursor:agent:create, cursor:models:list) in the LiteLLM Logs page. Since Cursor's API is subscription-based, costs are tracked as $0.00 per request.
• UI Support: Integrated the correct Cursor hexagonal logo and updated UI components (provider_info_helpers.tsx, provider_create_fields.json) to allow users to easily add Cursor API credentials via the LLM Credentials UI, with https://api.cursor.com as the default API Base.
• Documentation: Created a new documentation page (docs/pass_through/cursor.md) with a simplified, UI-focused tutorial on how to add Cursor credentials, make API calls through the proxy, and view logs, matching the existing a2a_cost_tracking style.
• Testing: Added 18 new unit tests for the Cursor pass-through routes and logging handler, ensuring robust functionality. Live proxy tests and UI demonstrations confirmed end-to-end integration.

---

  

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
litellm	Error		Feb 28, 2026 8:48pm

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[greptile-apps]

Greptile Summary

This PR adds native pass-through support for Cursor Cloud Agents, allowing users to manage Cursor agents via the LiteLLM proxy. The implementation follows established patterns (Cohere, Gemini, etc.) with a dedicated route (/cursor/{endpoint:path}), Basic Auth credential handling, a logging handler that classifies Cursor API operations, UI integration, and documentation.

• New pass-through route at /cursor/{endpoint:path} with Basic Auth encoding of the Cursor API key, mirroring the Cohere pass-through pattern
• Logging handler (CursorPassthroughLoggingHandler) classifies 10 Cursor API operations (agent CRUD, models, repositories, etc.) and logs all requests at $0.00 cost (subscription-based)
• Route detection in success_handler.py has dead code in the is_cursor_route loop that can never return True — the method works correctly via its early return paths, but the loop should be removed for clarity
• UI and config additions (provider enum, logo, credential fields) follow existing patterns exactly
• Tests include 14+ unit tests across two files, all properly mocked with no real network calls

Confidence Score: 4/5

• This PR is safe to merge — it adds a new isolated provider integration with no changes to existing logic paths.
• The implementation cleanly follows established pass-through patterns, has good test coverage with properly mocked tests, and only touches new/additive code paths. The one minor issue (dead code in is_cursor_route) is non-functional. Score is 4 instead of 5 due to the dead code that could confuse future maintainers.
• litellm/proxy/pass_through_endpoints/success_handler.py — the is_cursor_route method contains dead code in its loop that should be cleaned up.

Important Files Changed

Filename	Overview
litellm/proxy/pass_through_endpoints/llm_passthrough_endpoints.py	Adds /cursor/{endpoint:path} pass-through route with Basic Auth encoding, following the same pattern as the Cohere route. Clean implementation.
litellm/proxy/pass_through_endpoints/llm_provider_handlers/cursor_passthrough_logging_handler.py	New logging handler with request classification for Cursor Cloud Agents API operations. Well-structured with proper error handling and fallback.
litellm/proxy/pass_through_endpoints/success_handler.py	Integrates Cursor handler into the pass-through logging chain. The is_cursor_route method contains dead code in its loop that can never return True, but the method still works correctly via its early return paths.
litellm/types/utils.py	Adds CURSOR to LlmProviders enum. Single-line, low-risk change.
litellm/proxy/_types.py	Adds /cursor to LiteLLMRoutes pass-through list. Single-line change consistent with other providers.
tests/test_litellm/proxy/pass_through_endpoints/llm_provider_handlers/test_cursor_passthrough_logging_handler.py	Well-structured unit tests covering request classification, route detection, and logging handler behavior. All tests use mocks — no real network calls.
tests/test_litellm/proxy/pass_through_endpoints/test_llm_pass_through_endpoints.py	Adds 4 new tests for the Cursor proxy route covering Basic Auth, missing API key, custom API base, and agent launch. All properly mocked.
ui/litellm-dashboard/src/components/provider_info_helpers.tsx	Adds Cursor to the UI provider enum, logo map, provider map, and placeholder model. Follows existing patterns exactly.
litellm/proxy/public_endpoints/provider_create_fields.json	Adds Cursor provider configuration with api_key and api_base credential fields. Follows existing JSON schema pattern.
docs/my-website/docs/pass_through/cursor.md	New documentation page for Cursor Cloud Agents pass-through with Quick Start, API examples, and endpoint reference table.
docs/my-website/sidebars.js	Adds Cursor doc page to the pass-through section of the sidebar in alphabetical order.

Sequence Diagram

sequenceDiagram
    participant Client
    participant LiteLLM Proxy
    participant cursor_proxy_route
    participant create_pass_through_route
    participant Cursor API

    Client->>LiteLLM Proxy: POST /cursor/v0/agents<br/>Authorization: Bearer <litellm-key>
    LiteLLM Proxy->>cursor_proxy_route: Route matched
    cursor_proxy_route->>cursor_proxy_route: get_credentials("cursor")
    cursor_proxy_route->>cursor_proxy_route: Base64 encode API key for Basic Auth
    cursor_proxy_route->>create_pass_through_route: target=api.cursor.com/v0/agents<br/>custom_headers={Authorization: Basic ...}<br/>custom_llm_provider="cursor"
    create_pass_through_route->>Cursor API: POST /v0/agents<br/>Authorization: Basic <base64(key:)>
    Cursor API-->>create_pass_through_route: 200 {id, name, status}
    create_pass_through_route->>LiteLLM Proxy: PassThroughEndpointLogging
    LiteLLM Proxy->>LiteLLM Proxy: is_cursor_route() → CursorPassthroughLoggingHandler
    LiteLLM Proxy->>LiteLLM Proxy: _classify_cursor_request() → "cursor:agent:create"
    LiteLLM Proxy-->>Client: 200 {id, name, status}

Loading

_{Last reviewed commit: 9f5b31d}

[greptile-apps]

_{15 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Dead code in is_cursor_route loop

The for loop on lines 422-426 can never return True. Here's why:

1. Line 417-418: if custom_llm_provider == "cursor", return True immediately.
2. Line 419-421: if hostname is api.cursor.com, return True immediately.
3. Line 426: return custom_llm_provider == "cursor" — but we already know custom_llm_provider != "cursor" (that was handled in step 1), so this always evaluates to False.

The method works correctly in practice because the proxy route always passes custom_llm_provider="cursor", which is caught by the early return. However, the loop gives a false impression of additional detection logic. Consider simplifying:

Suggested change

	def is_cursor_route(
	self, url_route: str, custom_llm_provider: Optional[str] = None
	):
	"""Check if the URL route is a Cursor Cloud Agents API route."""
	if custom_llm_provider == "cursor":
	return True
	parsed_url = urlparse(url_route)
	if parsed_url.hostname and "api.cursor.com" in parsed_url.hostname:
	return True
	for route in self.TRACKED_CURSOR_ROUTES:
	if route in url_route:
	path = parsed_url.path if parsed_url.scheme else url_route
	if path.startswith("/v0/"):
	return custom_llm_provider == "cursor"
	return False
	def is_cursor_route(
	self, url_route: str, custom_llm_provider: Optional[str] = None
	):
	"""Check if the URL route is a Cursor Cloud Agents API route."""
	if custom_llm_provider == "cursor":
	return True
	parsed_url = urlparse(url_route)
	if parsed_url.hostname and "api.cursor.com" in parsed_url.hostname:
	return True
	return False