Refactor terminology from "LLM *" to "AI *" across AI Workspace#2648
Refactor terminology from "LLM *" to "AI *" across AI Workspace#2648Thushani-Jayasekera wants to merge 2 commits into
Conversation
This commit updates various components and pages to replace instances of "LLM Provider" and related terms with "AI Provider" for consistency and clarity. Changes include updates in Cypress tests, UI components, and documentation references, ensuring a unified terminology throughout the application.
…ation This commit updates various components, tests, and UI elements to replace instances of "LLM Proxy" with "AI Proxy" for consistency and clarity. Changes include updates in Cypress tests, UI components, and documentation references, ensuring a unified terminology throughout the application.
|
Warning Review limit reached
Next review available in: 37 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (36)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
1 participant
UI Terminology Rename: "LLM Provider" → "AI Provider", "LLM Proxy" → "AI Proxy"
Date: 2026-07-13
Scope:
portals/ai-workspace— user-visible UI strings onlyWhy
chat/completionsis not the only resource the platform supports — providers can alsoserve embeddings, image models, and other AI resources, so "LLM Provider" sounds
limiting. "AI Provider" matches how the product is described to buyers in practice. "AI Proxy" follows
for consistency — a proxy fronting an AI Provider that serves embeddings is not an
"LLM" proxy.
What changed
Display-level rename only, case-preserving:
Covered surfaces: sidebar navigation, page titles and descriptions, buttons, form
labels and helper texts, drawers, delete-confirmation dialogs, error/success
snackbars, empty states, org-limit warnings, quick-start banners, Explore More cards,
and the login/register feature bullets. Cypress assertions on the renamed labels were
updated to match ("LLM Provider Templates", "Create/Delete App AI Proxy").
What deliberately did NOT change
LLMProxyNew.tsx,llmProviderApis.ts),context names, entity kind values (
LlmProvider,LlmProxy), routes, and API paths.logger.*messages keep the old wording (not user-visible).Auto-generated secret for LLM provider/proxy ...) are backend payloads, not UI labels.Stats
tsc --noEmit: no new errors introduced (pre-existing errors on thebranch are unrelated to string literals).