Skip to content

feat(tui): add search/filter to provider picker in setup wizard #392

Closed

Description

@Ashwinhegde19

Problem

The provider picker in the setup wizard (internal/tui/provider_wizard.go) is a plain scrollable list with no search/filter capability. With 28+ providers now available, scrolling to find a specific provider is tedious.

The model picker (internal/tui/picker.go) already has search via commandPicker.applyQuery() — case-insensitive substring matching on model fields. The provider picker lacks the equivalent.

Requested behavior

Add a search/filter input to the provider step of the setup wizard, similar to how the model picker works:

  • Typing filters the provider list in real-time (case-insensitive substring match on provider name, ID, and aliases)
  • Clear display showing active filter state
  • Backspace to delete filter characters
  • Arrow keys navigate filtered results

Why it belongs in Zero

  • 28+ providers now makes the scrollable list cumbersome
  • Consistency with the model picker UX (which already has search)
  • Improves first-run setup experience

Alternatives or workarounds considered

  • Users can scroll through the full list (current behavior)
  • The list is sorted by catalog order, which helps, but doesn't solve the discoverability problem

Implementation details

The model picker search in internal/tui/picker.go:94 (applyQuery()) already implements case-insensitive substring filtering. The provider wizard's model step (internal/tui/provider_wizard.go:1484) also has filteredModels() with the same pattern. The provider step needs an equivalent filteredProviders() method and a providerSearch field.

The fuzzySubsequenceGap() function in internal/tui/autocomplete.go:643 could also be reused if fuzzy matching is preferred over simple substring matching.

Examples, screenshots, or prior discussion

  • Provider wizard: internal/tui/provider_wizard.go:1245 (renderProviderStep)
  • Model picker search: internal/tui/picker.go:94 (applyQuery)
  • Provider wizard model search: internal/tui/provider_wizard.go:1427 (renderModelSearch)

Activity

  1. eli-l commented on Jul 2, 2026

    @eli-l
    Contributor

    #393

    Tested on opencode.
    When added - models are discovered by default. PR adds "models" key to the provider, to store the available models.
    Also same model might be served by the different providers, therefore favorites must use unique provider+model ID, as model ID is not unique.

  2. added a commit that references this issue on Jul 4, 2026
    2fcea71
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions