fix(ui): remove Chat item from dashboard leftnav

[devin-ai-integration]

Relevant issues

Linear ticket

Pre-Submission checklist

• I have added meaningful tests
• My PR passes all CI/CD checks (e.g., lint, format, unit tests)
• My PR's scope is as isolated as possible; it only solves 1 specific problem
• I have received a Greptile Confidence Score of at least 4/5 before requesting a maintainer review

Screenshots / Proof of Fix

UI-only change. Before: the AI Gateway section of the leftnav rendered a "Chat" entry (when enable_chat_ui was on). After: the entry is gone regardless of the setting

Type

🧹 Refactoring

Changes

Removes the "Chat" nav item from the dashboard leftnav and the now-dead enableChatUI plumbing that only existed to gate it

• leftnav.tsx: drop the chat menu entry, the item.key === "chat" filter branch, the enableChatUI prop, and the now-unused MessageSquare import
• SidebarProvider.tsx: drop the enableChatUI state, its getUISettings read, and the prop passthrough
• leftnav.test.tsx: remove the two Chat-visibility tests that asserted the removed behavior

The /chat route and the enable_chat_ui admin toggle are left untouched; only the sidebar entry is removed. enable_chat_ui still gates direct access to the /chat page via its layout, so the toggle text mentioning the sidebar is now slightly stale; happy to also drop the toggle if you'd prefer the feature fully gone

Final Attestation

• The tests check the right things, including the edge cases, and regressions in the respective real-world customer use-cases are not possible after this PR

Link to Devin session: https://app.devin.ai/sessions/5714abeea5ef4d79a176a7f76a31ddad
Requested by: @krrish-berri-2

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[CLAassistant]

)
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement) before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck) it.}

[greptile-apps]

Greptile Summary

This PR removes the "Chat" entry from the dashboard left-nav — including the enableChatUI prop and state that gated it, the item.key === \"chat\" filter branch, the MessageSquare icon import, and the two unit tests that validated the now-deleted behaviour. The /chat route and the enable_chat_ui backend toggle are left intact.

• leftnav.tsx / SidebarProvider.tsx: the removal is complete and internally consistent — no dead state, dead props, or dead filter branches remain.
• leftnav.test.tsx: the two deleted tests covered only the removed feature and would have failed at compile-time after the prop was dropped, so their removal is correct and does not weaken coverage.
• One loose end (not in the diff): the fallback description string in UISettings.tsx still tells admins the toggle "shows the Chat page in the UI sidebar", which is no longer true.

Confidence Score: 4/5

Safe to merge — the change is a clean, self-contained UI removal with no runtime risk.

All three files are internally consistent: the prop, state, filter branch, icon import, and tests are removed together with no dangling references. The only rough edge is that the admin-settings description for enable_chat_ui in the unchanged UISettings.tsx now describes behaviour that no longer exists in the sidebar, which could confuse administrators.

The unchanged UISettings.tsx has a stale fallback description string for the enable_chat_ui toggle that now describes a sidebar entry that no longer exists.

Important Files Changed

Filename	Overview
ui/litellm-dashboard/src/components/leftnav.tsx	Removes the "chat" menu entry, its associated filter predicate, the enableChatUI prop from SidebarProps, and the now-unused MessageSquare icon import — all consistently and without leaving dead branches.
ui/litellm-dashboard/src/app/(dashboard)/components/SidebarProvider.tsx	Drops the enableChatUI React state, the getUISettings branch that populated it, and the prop passthrough to Sidebar — fully consistent with the leftnav change.
ui/litellm-dashboard/src/components/leftnav.test.tsx	Removes the two tests that asserted Chat-item visibility behaviour; appropriate cleanup since the feature under test is removed, not broken.

_{Reviews (1): Last reviewed commit: "fix(ui): remove Chat item from dashboard..." | Re-trigger Greptile}

[greptile-apps]

Stale admin-settings description for enable_chat_ui

UISettings.tsx (line 366) still renders the fallback description "If enabled, shows the Chat page in the UI sidebar…". After this PR the toggle no longer controls a sidebar entry, so an admin who reads that description will be misled about what the setting does. The toggle still has a real effect (gating direct /chat route access via the layout), but the description doesn't reflect that. Updating the fallback string (or the backend schema description) to describe the remaining behaviour would close the gap the PR description already acknowledges.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[codspeed-hq]

Merging this PR will not alter performance

✅ 31 untouched benchmarks

---

_{Comparing litellm_remove_chat_leftnav_1784260812 (74a0ff1) with litellm_internal_staging (9cae6fa)}