Skip to content

docs(guardrails): LLM Shield Proxy: which LiteLLM versions include it; quick start runs as written - #2138

Open
ninadphalak wants to merge 3 commits into
BerriAI:mainfrom
ninadphalak:docs/llm-shield-proxy-version-note
Open

ninadphalak wants to merge 3 commits into
BerriAI:mainfrom
ninadphalak:docs/llm-shield-proxy-version-note

Conversation

@ninadphalak

@ninadphalak ninadphalak commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Follow-up to #2070, from running the page as written on the current image.

Version note. llm_shield_proxy was merged on 2026-10-05 (BerriAI/litellm#42645); the first release that includes it is the v1.106.0-dev.1 pre-release (checked: litellm==1.106.0.dev1 starts with the documented config and loads the guardrail; 1.105.0rc1 logs the skip line below). On ghcr.io/berriai/litellm:main-latest (1.105.0) the documented config.yaml is accepted, the proxy logs Skipping guardrail 'llm-shield': ... Unsupported guardrail: llm_shield_proxy, starts without it, and requests reach the provider unredacted. The page now says so in an info box that names v1.106.0-dev.1 as the first release with it.

Quick start as written. On main the proxy refuses to start without a master key, and step 4 used $LITELLM_API_KEY, which the page never set. Step 3 now exports LITELLM_MASTER_KEY (placeholder value, as in the other pages) and the two curl examples use it.

Checked on a running LiteLLM built from main at the merge commit with an LLM Shield Proxy container: with the master key set, steps 3 and 4 run as written and the reply comes back restored.

…e it, and make the quick start run as written
@vercel

vercel Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
litellm Error Error Oct 7, 2026 1:29pm UTC

Request Review

This branch had an error being deployed

1 failed deployment
Preview — 775608a0 Deployed Oct 7, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant