feat: add LiteLLM as AI gateway provider#1249
Open
RheagalFire wants to merge 5 commits into
Open
Conversation
Author
v1r3n
approved these changes
Jul 3, 2026
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.
Pull Request type
./gradlew spotlessApplyhas been run.Changes in this PR
Adds LiteLLM as a new AI gateway provider, giving Conductor users access to 100+ LLM providers through a single unified OpenAI-compatible interface.
LiteLLM is a user-deployed AI gateway/proxy that unifies 100+ providers (OpenAI, Anthropic, Azure, Bedrock, Vertex AI, Mistral, Cohere, etc.) behind one OpenAI-compatible endpoint. Users deploy it locally, via Docker, Kubernetes, or on AWS/GCP/Azure using Terraform modules, and point Conductor at it. This lets users route requests through one config, add cost tracking/rate limiting/fallbacks, and switch providers without changing workflow definitions.
Files added:
ai/src/main/java/.../providers/litellm/LiteLLM.java- new provider implementingAIModelviaOpenAICompatChatModel(same pattern as Grok/Perplexity). Zero new dependencies.ai/src/main/java/.../providers/litellm/LiteLLMConfiguration.java- Spring@ConfigurationProperties(prefix = "conductor.ai.litellm").base-urlis required (LiteLLM is user-deployed, no public SaaS endpoint).api-keyis optional (many deployments run without auth).ai/README.md- added LiteLLM to supported providers table (now 13), configuration docs, environment variables, anddrop_paramsguidance.Configuration:
Full E2E (Conductor server in Docker + Postgres + LiteLLM proxy -> Azure Foundry / Anthropic Claude Sonnet 4.6):
Complete chain verified: Conductor workflow ->
LLM_CHAT_COMPLETEtask -> LiteLLM provider ->OpenAICompatChatModel-> HTTP to LiteLLM proxy -> Azure Foundry -> Anthropic Claude -> response parsed back through the full Conductor pipeline.Example workflow:
{ "llmProvider": "litellm", "model": "gpt-4o", "messages": [{"role": "user", "message": "What is the capital of France?"}], "temperature": 0.7, "maxTokens": 500 }Set
drop_params: truein your LiteLLM proxy config (litellm_settings) so provider-unsupported parameters (e.g.frequency_penaltyfor Anthropic) are silently dropped instead of causing 400 errors.