Summary
We need a guided setup flow for configuring a web search provider, similar to the existing guided model setup flow.
Motivation
Today the model setup has a friendly, step-by-step guided experience (see design/model-setup-dialog/). Configuring a web search provider (e.g. Brave / BRAVE_API_KEY) has no equivalent guided experience — users must know where to get an API key and where to enter it. A guided flow would lower friction and make search-enabled skills work out of the box.
Proposed direction
- Mirror the model setup dialog pattern: introduce a guided, multi-step flow for choosing and configuring a web search provider.
- Walk the user through selecting a provider, obtaining an API key, entering/validating it, and confirming connectivity.
- Persist the provider selection + credentials consistent with existing config handling.
Design needed
Tagged design needed — UX/flow design for the provider selection, key acquisition guidance, and validation states is required before implementation.
Filed from a suggestion during development.
Summary
We need a guided setup flow for configuring a web search provider, similar to the existing guided model setup flow.
Motivation
Today the model setup has a friendly, step-by-step guided experience (see
design/model-setup-dialog/). Configuring a web search provider (e.g. Brave /BRAVE_API_KEY) has no equivalent guided experience — users must know where to get an API key and where to enter it. A guided flow would lower friction and make search-enabled skills work out of the box.Proposed direction
Design needed
Tagged design needed — UX/flow design for the provider selection, key acquisition guidance, and validation states is required before implementation.
Filed from a suggestion during development.