Repository navigation
[1/1 Provider onboarding] Preserve input and simplify setup - #160
Conversation
…ection Keep provider save feedback separate from Codex connection state. Supply an explicit private catalog without changing the original OpenAI provider identity, and bound repeated native turn requests to prevent duplicate upstream inference.
Use a two-step provider editor with encrypted draft and selection persistence. Load saved fields without treating a displayed key as a replacement, and add explicit reveal, copy, reload and reuse actions. Keep save failures editable and route a requested restart through the existing owner flow after the dialog closes.
Gaebabi
left a comment
There was a problem hiding this comment.
Author self-review of e3644b4 (not an independent approval). Reviewed the provider connection/catalog path, bounded turn-request receipts, encrypted editor draft/key semantics, both desktop editors, localization and the full final diff. Saved credentials stay protected and viewing/copying a key does not authorize a changed destination. No account/provider data, owner captures, dependencies or workflow changes are included.
The latest six required contexts pass on the current main base. Local verification passed 255 provider/editor/native CLI contracts, 350 account/recovery checks, 116 WPF component checks and 42 localization API checks; the Windows and shared builds pass. The attached application-component images are fictional offscreen renders. Owner desktop model-picker/provider inference acceptance and the broader issue #138 remain separate. The owner explicitly authorized merge after CI and a local Switch update while preserving live Codex work.
Problem and result
Provider settings were presented as one long form, save feedback hid a disconnected state, and switching providers or finishing an operation cleared key fields. The editor now uses two steps: connection details, then Connect/Restart. Optional model IDs and advanced controls are collapsed.
Related: #138. Existing router-pinned connections and account data are preserved; the broader external-provider and actual Codex-picker acceptance remains separate.
Validation
Screens
Korean component evidence.