…ings

Replace /agents/settings/models with a redirect to /ai/settings/models,
delete the now-dead ChatModelAdminPanel/ModelsSection/ProvidersSection and
old model/provider forms, extract the still-used ProviderField, repoint
inbound links, and drop dead chat provider mutations flagged by knip.

Co-authored-by: Coder Agent <agent@coder.com>

…nchronously

The submit button relied on Formik's isValid, which is briefly true under
validateOnMount because errors populate in a post-render effect. This raced
with the Add story's synchronous toBeDisabled assertion. Compute the
disabled state from the current values instead.

Co-authored-by: Coder Agent <agent@coder.com>

…dmin sidebar

Mirror the Providers external link with a Models item that points to
/ai/settings/models, using the arrow-up-right trailing icon.

Co-authored-by: Coder Agent <agent@coder.com>

Match the Providers page, which renders provider icons in a rounded-square
Avatar, in the Models list rows and the model form header for visual
consistency.

Co-authored-by: Coder Agent <agent@coder.com>

…ls page

The ChatModelAdminPanel ProviderIcon renders inside its own rounded-full
circle, so wrapping it in an Avatar still looked circular. Use the Providers
page ProviderIcon/getProviderIcon (plain logo in a rounded-square Avatar) in
the model rows, form header, provider select, and add-model dropdown so the
two settings pages match. Add the gemini icon mapping so model icons do not
regress.

Co-authored-by: Coder Agent <agent@coder.com>

…UX on Models

List rows now show an Enabled badge when enabled and no badge when disabled
(Default takes precedence), mirroring the Providers row. The model detail
page shows a Disabled badge by the title and moves the enabled toggle to a
Switch with an Enable label that persists immediately, instead of saving the
enabled state with the rest of the form.

Co-authored-by: Coder Agent <agent@coder.com>

…isabled status to model list

Add a Provider column showing each model's provider label, and present
status with the shared StatusIndicator (Active/Disabled with a status dot)
plus a Default sub-label, matching the new model list design. Model cost
remains omitted pending backend support.

Co-authored-by: Coder Agent <agent@coder.com>

Render the models table with client-side pagination (10 per page) using the
shared paginateItems helper and PaginationWidgetBase, plus a Showing X of Y
footer, matching the Figma.

Co-authored-by: Coder Agent <agent@coder.com>

Keep table rows a uniform 72px tall so the default model's 'Default'
sub-label no longer makes that row taller than the others, avoiding
layout shift on page changes.

…vatar spacing

Match the Figma spec: render the model name and provider name as
14px/24px medium text that truncates with an ellipsis (primary and
secondary content colors respectively), and give the provider avatar a
universal 16px of space by using a 40px (lg) avatar with 16px cell
padding in the 72px row.

The status label (Active/Disabled) rendered at text-xs (12px); bump it
to text-sm with a 24px line-height to match the Figma body
default/medium style. Color and weight already came from the success
StatusIndicator variant.

…der style

Render the context limit cell at text-sm/24px medium so it matches the
provider name typography.

… a dropdown

The Add model action was a dropdown that forced the admin to pick a
provider before opening the form. Replace it with a plain button that
links straight to the Add model page, and have that page default to the
first manageable provider so the provider becomes an in-form choice (it
remains selectable via the Provider field).

- Move the collapsible section chevrons (Cost tracking, Provider
  configuration, Advanced) to the left of their titles, with the
  description indented beneath the title.
- Group Cancel and Add Model together at the bottom-right; the edit-mode
  Delete button stays left-aligned.
- Drop the 'Configure connection details and credentials' subtitle that
  isn't in the design and right-align the edit-only enable toggle.
- Capitalize the context limit 'Tokens' suffix.

… form

Match the Figma input spec (40px tall, 12px horizontal padding) by
bumping the model form's inputs, selects, and input groups from h-9 to
h-10. The base Input/SelectTrigger already provide the 12px padding.
The provider-config segmented control grows to match (container h-10,
inner buttons h-9).

…puts

Match the Figma: each top-grid field shows its helper description
between the label and the input rather than below it. Adds the missing
'Unique identifier (used in urls, can't be changed)' description to the
model identifier field (replacing its info tooltip) and moves the
display name, context limit, and provider descriptions above their
controls.

…se switches

- Wrap Cost tracking, Provider configuration, and Advanced in a single
  rounded bordered panel, with interior padding and dividers between
  each section (instead of bare top-border separators).
- Render provider-configuration boolean options with the shared Switch
  component (switch + label + info icon), each on its own full-width
  row, replacing the On/Off segmented control.

…ith heading

Add pl-6 to each expanded section's content so the fields line up with
the section heading text rather than the chevron (chevron 16px + 8px
gap).

…downs

Reasoning effort and other enum options were shown as a segmented
button control; render them as a Select dropdown (matching the Figma)
with capitalized option labels. Removes the now-unused SegmentedField.

…switches

Make enum dropdowns compact (single grid column) instead of full-width
so the input and dropdown fields (thinking budget tokens, thinking
display, reasoning effort) sit inline in the grid row, with the
boolean switches stacked full-width below them.

…data

Drive conditional field visibility and mutual exclusivity from the
generated model-options schema instead of hardcoding field names in the
frontend.

- codersdk/chats.go: tag the web-search domain/context fields with
  visible_when="web_search_enabled", and mark anthropic allowed/blocked
  domains as conflicts_with each other.
- scripts/modeloptionsgen: emit the new visible_when and conflicts_with
  metadata; regenerate chatModelOptionsGenerated.json.
- site ModelConfigFields: generically hide fields until their
  visible_when sibling is enabled, and disable a field while a
  conflicts_with sibling holds a value (recoverable if both are set).

This keeps the source of truth in the Go structs, so new dependent or
mutually exclusive fields work without frontend changes.

Only show the JSON array/object validation error once the field has
been blurred, so typing a partial value like "[" no longer complains
mid-edit. Submit remains blocked while the value is invalid.

Remove the footer's top border so there's no extra divider line between
the enclosed configuration panel and the Cancel/Save buttons.

…iting

Drop the mr-auto so the edit-mode Delete button sits in the right-hand
button group next to Save instead of being pushed to the left.

…er color on display name

Generated by Coder Agents.

…re base component defaults

Remove redundant h-10 (base Input/SelectTrigger/InputGroup/Autocomplete
are already h-10) and redundant text-sm/font-medium on Labels (base Label
already sets them) across the model form fields.

Generated by Coder Agents.

…on base 14px/12px

Tailwind orders the arbitrary text-[13px] before the named text-sm/text-base
scale, so it never won over the base component font size. Removing it leaves
fields/labels at the base 14px (text-sm) and helper text at 12px (text-xs),
matching the Figma type scale.

Generated by Coder Agents.