docs: add LiteLLM proxy bundle

[mendonk]

#11805

Summary by CodeRabbit

Documentation

• Added comprehensive documentation for the LiteLLM bundle, detailing LiteLLM Proxy setup and configuration for routing API requests across multiple LLM providers using a single authentication key. Includes full parameter reference, output descriptions, and guidance on when to use each available output type.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Walkthrough

A new documentation file for the LiteLLM bundle is added, describing how the LiteLLM Proxy routes requests to multiple LLM providers with parameter documentation. The sidebar navigation is updated to include this new bundle documentation.

Changes

Cohort / File(s)	Summary
Documentation docs/docs/Components/bundles-lite-llm.mdx	New documentation introducing the LiteLLM bundle and LiteLLM Proxy, covering request routing to multiple LLM providers, parameter configurations (api_base, api_key, model_name, temperature, max_tokens, timeout, max_retries, stream), and usage guidance.
Navigation docs/sidebars.js	Sidebar entry added for the new LiteLLM bundle documentation in the Components/Bundles section.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 7

✅ Passed checks (7 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly and clearly summarizes the main change: adding documentation for the LiteLLM proxy bundle component.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Test Coverage For New Implementations	✅ Passed	Pull request contains only documentation changes with no new code implementation or functionality changes requiring tests.
Test Quality And Coverage	✅ Passed	This PR contains only documentation and configuration changes (markdown files and sidebar.js updates) with no code implementation requiring tests.
Test File Naming And Structure	✅ Passed	PR contains only documentation changes; no test files added or modified. Documentation does not require unit tests, and the existing component already has tests.
Excessive Mock Usage Warning	✅ Passed	PR contains only documentation changes (markdown file and sidebar config) with no test files or mock objects.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch docs-llmproxy-component

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Frontend Unit Test Coverage Report

Coverage Summary

Lines	Statements	Branches	Functions
	22.04% (7566/34320)	14.69% (3947/26855)	14.88% (1081/7261)

Unit Test Results

Tests	Skipped	Failures	Errors	Time
2507	0 💤	0 ❌	0 🔥	42.688s ⏱️

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 35.31%. Comparing base (f44e2b3) to head (1d89bbf).
⚠️ Report is 190 commits behind head on docs-1.8-release.

❌ Your project check has failed because the head coverage (42.03%) is below the target coverage (60.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

@@                 Coverage Diff                  @@
##           docs-1.8-release   #11867      +/-   ##
====================================================
- Coverage             35.31%   35.31%   -0.01%     
====================================================
  Files                  1525     1525              
  Lines                 73292    73292              
  Branches              11021    11021              
====================================================
- Hits                  25884    25883       -1     
  Misses                45995    45995              
- Partials               1413     1414       +1     

Flag	Coverage Δ
backend	55.77% <ø> (ø)
frontend	16.99% <ø> (ø)
lfx	42.03% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 8 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/docs/Components/bundles-lite-llm.mdx`:
- Around line 1-4: The front matter for the documentation page with title
"LiteLLM" and slug "/bundles-lite-llm" is missing required fields; update the
YAML front matter block at the top of the file to include a descriptive
`description` string summarizing the page and add a numeric `sidebar_position`
(e.g., 1, 2, etc.) to control ordering; ensure the block contains `title`,
`description`, and `sidebar_position` keys alongside the existing `slug`.
- Line 33: Update the table row for the `api_key` parameter so its "type" column
reads `String` (not "Virtual Key"), keeping the description text that explains
it is a virtual key for LiteLLM proxy authentication; modify the `api_key` row
in the bundles-lite-llm.mdx table to reflect the correct data type while
preserving the existing semantics in the description column.

---

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f44e2b3 and 1d89bbf.

📒 Files selected for processing (2)

• docs/docs/Components/bundles-lite-llm.mdx
• docs/sidebars.js

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Front matter is missing required description and sidebar_position fields.

📝 Proposed fix

 ---
 title: LiteLLM
+description: Use the LiteLLM bundle to route LLM requests through a LiteLLM proxy with a single virtual key.
 slug: /bundles-lite-llm
+sidebar_position: 1
 ---

As per coding guidelines, "Front matter should include 'title', 'description', and 'sidebar_position' fields for documentation pages."

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	---
	title: LiteLLM
	slug: /bundles-lite-llm
	---
	---
	title: LiteLLM
	description: Use the LiteLLM bundle to route LLM requests through a LiteLLM proxy with a single virtual key.
	slug: /bundles-lite-llm
	sidebar_position: 1
	---

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/docs/Components/bundles-lite-llm.mdx` around lines 1 - 4, The front
matter for the documentation page with title "LiteLLM" and slug
"/bundles-lite-llm" is missing required fields; update the YAML front matter
block at the top of the file to include a descriptive `description` string
summarizing the page and add a numeric `sidebar_position` (e.g., 1, 2, etc.) to
control ordering; ensure the block contains `title`, `description`, and
`sidebar_position` keys alongside the existing `slug`.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

api_key type should be String, not Virtual Key.

"Virtual Key" describes the semantics of the value, not its data type — inconsistent with every other row in the table. The description column already captures that it's a virtual key.

📝 Proposed fix

-| api_key | Virtual Key | Input parameter. Virtual key for authentication with the LiteLLM proxy. |
+| api_key | String | Input parameter. Virtual key for authentication with the LiteLLM proxy. |

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	| api_key | Virtual Key | Input parameter. Virtual key for authentication with the LiteLLM proxy. |
	| api_key | String | Input parameter. Virtual key for authentication with the LiteLLM proxy. |

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/docs/Components/bundles-lite-llm.mdx` at line 33, Update the table row
for the `api_key` parameter so its "type" column reads `String` (not "Virtual
Key"), keeping the description text that explains it is a virtual key for
LiteLLM proxy authentication; modify the `api_key` row in the
bundles-lite-llm.mdx table to reflect the correct data type while preserving the
existing semantics in the description column.

[aimurphy]

I agree with coderabbit here. Type should be either string or secret string

[coderabbitai]

@aimurphy Thank you for confirming! Yes, "String" or "Secret String" would both be more appropriate type values for the table, as they describe the data type rather than the semantic meaning. The description column already explains that it's a virtual key for LiteLLM proxy authentication.

---

🧠 Learnings used

Learnt from: TensorNull
Repo: langflow-ai/langflow PR: 9735
File: docs/docs/Components/bundles-cometapi.mdx:9-9
Timestamp: 2025-09-07T05:44:46.715Z
Learning: In Langflow bundle documentation files (docs/docs/Components/bundles-*.mdx), the standard link pattern for referencing the main Bundles page is [Bundles](/components-bundle-components), not /components-bundles. This pattern is used consistently across all 37+ bundle documentation files.

[aimurphy]

approved with one small comment

[aimurphy]

I agree with coderabbit here. Type should be either string or secret string

[github-actions]

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft