fix: update disabled state on AI provider rows by tracyjohnsonux · Pull Request #28558 · coder/coder · GitHub
Skip to content

fix: update disabled state on AI provider rows - #28558

Merged
tracyjohnsonux merged 12 commits into
mainfrom
ai-providers-disabled-row-state
Aug 26, 2026
Merged

fix: update disabled state on AI provider rows#28558
tracyjohnsonux merged 12 commits into
mainfrom
ai-providers-disabled-row-state

Conversation

@tracyjohnsonux

Copy link
Copy Markdown
Contributor

Updates the AI providers list to make the disabled state visible on the row itself. Disabled providers show a Disabled badge beside the name, a muted avatar, and disabled text for the name and base URL. The Enabled badge is removed from the status column, which now holds only issue badges (Not supported in Agents and Warning).

Also fixes tooltip inconsistency in the status column: the Not supported in Agents badge used a native title attribute while the warning used the shared Tooltip component, so they looked different. Both now use the shared tooltip, with a max width so long warnings wrap instead of rendering as one long line.

Storybook interaction coverage: new Disabled/Enabled stories, and NotSupportedInAgents now hovers the badge and asserts the shared tooltip content.


Created by Coder Agents on behalf of @tracyjohnsonux.

Move the enabled/disabled state out of the status column: disabled
providers now show a Disabled badge beside the name with a muted
avatar and disabled text for the name and base URL. The status column
keeps only the issue badges.

Replace the native title tooltip on the Not supported in Agents badge
with the shared Tooltip component so it matches the warning tooltip,
and constrain tooltip width so long warnings wrap.
@tracyjohnsonux
tracyjohnsonux marked this pull request as ready for review August 25, 2026 18:15

@ibetitsmike ibetitsmike left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Disclosure: This review was researched and written by Xum, an AI coding agent, acting for @ibetitsmike.

Ran the repo frontend-review audit (FE1-FE10) over the merge-base diff (3 files under site/src/).

FE1  PASS  Disabled story added; NotSupportedInAgents + WithHostnameCollisionWarning play fns exercise the new states
FE2  PASS  AIProvider from api/typesGenerated; no any / casts / non-null assertions
FE3  PASS  Badge / Tooltip / Avatar / Table primitives reused
FE4  PASS  event-bubbling isolation comments explain rationale
FE5  PASS  enabled / disabled / warning / unsupported states covered
FE6  PASS  status badges are semantic button triggers; accessible names lead with visible text
FE7  PASS  n/a - no query changes
FE8  PASS  n/a - no effects
FE9  PASS  MockAIProvider spread from testHelpers
FE10 PASS  role/text queries only

Notes:

  • Tooltip triggers stop click/keydown/keyup propagation so useClickableTableRow navigation is not hijacked - nice.
  • Pre-existing, untouched: isLoading || isFetching at ProvidersPageView.tsx:113.

Verdict: clean per the FE rule contract; no blocking findings. CI green at a473261f.

…-row-state

# Conflicts:
#	site/src/pages/AISettingsPage/ProvidersPage/components/ProviderRow.stories.tsx
#	site/src/pages/AISettingsPage/ProvidersPage/components/ProviderRow.tsx
@tracyjohnsonux
tracyjohnsonux enabled auto-merge (squash) August 26, 2026 18:28
@tracyjohnsonux
tracyjohnsonux merged commit c0e6818 into main Aug 26, 2026
26 checks passed
@tracyjohnsonux
tracyjohnsonux deleted the ai-providers-disabled-row-state branch August 26, 2026 19:00
@github-actions github-actions Bot locked and limited conversation to collaborators Aug 26, 2026
@tracyjohnsonux tracyjohnsonux changed the title feat(site): show disabled state on AI provider rows fix: show disabled state on AI provider rows Aug 26, 2026
@tracyjohnsonux tracyjohnsonux changed the title fix: show disabled state on AI provider rows fix: update disabled state on AI provider rows Aug 26, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants