fix(ui): add searchable filter to User Usage page

[xykong]

Description

Fixes #25750

The User Usage filter only showed a static preloaded list. Users could not type to search for a specific user, unlike the Global Usage page which supports debounced server-side search.

This PR introduces UserSingleSelect — a dedicated single-select component with useInfiniteUsers + 300ms debounce + infinite scroll — and wires it into EntityUsage for entityType === "user".

Root Cause

EntityUsage.tsx delegated user filtering to UsageExportHeader, which renders a plain <Select> without showSearch/onSearch. The same issue was fixed for Team Usage in PR #25107 using TeamMultiSelect.

Changes

• ui/litellm-dashboard/src/components/common_components/user_single_select.tsx — new component
• ui/litellm-dashboard/src/components/common_components/user_single_select.test.tsx — 10 tests
• ui/litellm-dashboard/src/components/UsagePage/components/EntityUsage/EntityUsage.tsx — wire up UserSingleSelect for entityType === "user"
• ui/litellm-dashboard/src/components/UsagePage/components/EntityUsage/EntityUsage.test.tsx — add mock for user_single_select

Testing

cd ui/litellm-dashboard
npx vitest run src/components/UsagePage/components/EntityUsage/ --reporter=verbose
npx vitest run src/components/common_components/user_single_select.test.tsx --reporter=verbose

All 92 existing tests pass + 10 new tests for UserSingleSelect.

Related

• Fixes [Bug] User Usage filter does not support text search/input unlike Global Usage #25750
• Mirrors the approach from PR fix(ui): add paginated team search to usage page filter #25107 (Team Usage fix)
• Original User Usage introduced in PR feat(ui): add user filtering to usage page #22059

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
litellm	Ready	Preview, Comment	Apr 15, 2026 4:53am

[greptile-apps]

Too many files changed for review. (937 files found, 100 file limit)

[CLAassistant]

All committers have signed the CLA.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Generic High Entropy Secret	da67018fe3d06730f1d212c99124966a6cde0463	litellm/proxy/management_endpoints/sso/happyelements_endpoints.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[xykong]

Rebuilt this PR as a clean, focused branch on top of berri/main:

• Removed all unrelated commits (SSO, VOD, otel, etc.) — those were internal patches that accidentally leaked into this branch
• Single commit with only the 4 files changed for the User Usage searchable filter
• No secrets or internal code — GitGuardian warning is now resolved
• CLA: all commits are now from the GitHub account (xy.kong@gmail.com), so both committers are signed ✅

The fix itself is unchanged: adds UserSingleSelect component using useInfiniteUsers with 300ms debounce, mirroring the TeamMultiSelect pattern from #25107.

[codspeed-hq]

Merging this PR will not alter performance

✅ 16 untouched benchmarks

---

_{Comparing xykong:fix/user-usage-searchable-filter (5d21637) with main (3e1479c)}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.