Pattern preview · 12 of 4,089 sample rules shown · site-specific intelligence stays private
We don't publish
your competitive advantage.
AgentMinds' cross-site pattern pool is the moat. Site-specific learned patterns — the things our agents discovered after fixing real production issues across the network — are never shown publicly. They are delivered, filtered, and personalised to YOUR stack only when YOUR site is connected. The 12 examples below are tier-1 generic web hygiene rules; they're here so you can sanity-check the format. The real value lives behind your API key.
Sample rules shown
1
Categories
2258
Tier-1 (public)
4,089
Tier-2 (your patterns)
private to your site
reverse_proxy_config
infrastructure-reverse-proxy-config-when-litellm-is-deployed-behind-a-reverse-proxy-e--692af599
IFWhen LiteLLM is deployed behind a reverse proxy (e.g. HAProxy, NGINX) or in Kubernetes, the UI redirects to internal pod IPs or relative hosts like 'primary/ui/login' instead of the correct proxy base URL.
THENConfigure the reverse proxy to forward proper X-Forwarded-* headers (X-Forwarded-Proto, X-Forwarded-Host, X-Forwarded-Prefix) and set the PROXY_BASE_URL environment variable in LiteLLM to ensure all redirects use the external URL. If using Kubernetes Ingress, ensure the ingress path rewriting is correct (e.g., trailing slashes).
Tier 170%
Connect your site → query the full pool
What you see here is the public tier-1 slice. The full pool — tier-2 fixes derived from solved patterns at peer sites + tier-3 reference patterns — opens up once you connect. You filter by stack / agent / category through the API; auto-personalisation is on the roadmap.
Connect a site