ui: clarify weight, alias, and denylist tooltips

[Pratham-Mishra04]

Summary

Improves the clarity of tooltip text across the API key configuration form to better explain how weights, model allowlists, denylists, and aliases interact with each other and with adaptive load balancing.

Changes

• Added a note to the weight tooltip clarifying that weights are not used when adaptive load balancing is enabled, and that key selection is instead based on live performance.
• Expanded the allowed models tooltip to explain that aliases must be added by their alias name — listing only the underlying model does not grant access to aliases pointing to it.
• Expanded the denylist tooltip to clarify that blocking an underlying model does not block aliases that point to it; aliases must be blocked by their alias name.
• Replaced em dashes (—) with hyphens (-) for consistency across tooltip and description text.
• Increased TooltipContent max width to max-w-sm where needed to accommodate the longer descriptions.

Type of change

• Bug fix
• Feature
• Refactor
• Documentation
• Chore/CI

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (React)
• Docs

How to test

Navigate to the provider API key configuration form and hover over the info icons next to:

• The Weight field — confirm the tooltip mentions adaptive load balancing behavior.
• The Allowed Models field — confirm the tooltip explains alias name requirements.
• The Denied Models field — confirm the tooltip explains that aliases are matched by alias name, not underlying model.

cd ui
pnpm i || npm i
pnpm build || npm run build

Screenshots/Recordings

Before/after screenshots of the updated tooltips recommended to confirm text renders correctly within the max-w-sm constraint.

Breaking changes

• No

Related issues

Security considerations

None.

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable

Summary by CodeRabbit

• Documentation
  • Enhanced and clarified help text descriptions and tooltips in the API key configuration interface to provide improved user guidance on adaptive load balancing behavior, weight settings configuration, model alias matching requirements for allow and deny lists, denylist precedence rules, optional deployment configuration options, and Azure credential setup details.

[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.}

[Pratham-Mishra04]

• ui: clarify weight, alias, and denylist tooltips #4309 👈 (View in Graphite)
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: acfcf4ac-92da-497e-a412-ca3b625d3c0c

📥 Commits

Reviewing files that changed from the base of the PR and between 059b829 and 7ffa400.

📒 Files selected for processing (1)

• ui/app/workspace/providers/fragments/apiKeysFormFragment.tsx

---

📝 Walkthrough

Walkthrough

This PR updates helper tooltips and field descriptions in the API Keys form fragment to clarify behavior for weight-based load balancing, alias model specification, denylist precedence, optional deployments field, and Azure credential detection.

Changes

API Keys Form Tooltips

Layer / File(s)	Summary
Tooltip and description text updates ui/app/workspace/providers/fragments/apiKeysFormFragment.tsx	Weight tooltip now mentions adaptive load balancing; Allowed Models tooltip clarifies alias-name specification; Blocked Models tooltip clarifies denylist precedence and alias-matching semantics; Deployments description text is rewrapped; Azure Default Credential description is expanded with detection/usage phrasing.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Tooltips now shine with clarity bright,
Weights and models balanced just right,
Aliases explained, denylists clear,
Azure credentials without fear,
Form helpers now guide users true!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically summarizes the main change: clarifying tooltip text for weight, alias interactions, and denylist behavior in the API keys form.
Description check	✅ Passed	The PR description comprehensively covers all required template sections including summary, changes, type, affected areas, testing instructions, breaking changes, and checklist, with detailed explanations of each tooltip update.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 06-12-chore_ui_tooltips_updates

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[greptile-apps]

Confidence Score: 5/5

Pure tooltip text and description copy changes with no logic, state, or component structure modifications — safe to merge.

All changes are confined to static tooltip strings and prose descriptions. No data-testid attributes were removed or altered, no component logic was touched, and the only structural change is adding max-w-sm to two TooltipContent elements that already used it elsewhere in the same file. The new alias/adaptive-load-balancing copy accurately reflects the system behavior described in the PR.

No files require special attention.

Important Files Changed

Filename	Overview
ui/app/workspace/providers/fragments/apiKeysFormFragment.tsx	Tooltip text improvements for weight, allowed models, and denylist fields; em dashes replaced with hyphens; max-w-sm added to two TooltipContent components. No logic or data-testid changes.

_{Reviews (1): Last reviewed commit: "chore: ui tooltips updates" | Re-trigger Greptile}