First-run UX bug surfaced by an end-to-end probe: after the user adds the "OpenAI Codex (local CLI)" connection from Settings -> Connections -> Add provider, every model in the form starts UNCHECKED. The user saves, returns to the chat composer, opens the model picker -- and the "Connected" tab is missing because no Codex models are enabled. The user has to re-open the connection, tick at least one model, save again, then return to chat. Two round-trips to make a feature work that the rest of the UI already advertises as installed. Anthropic / OpenAI / OpenRouter all keep their explicit-opt-in defaults because the model choice has billing and capability impact. Codex is the local CLI on the same machine -- the SDK accepts any model id, the "default_models" list is the SDK's curated shortlist, and gating chat behind a manual click adds friction without buying anything. Pre-checking all default models for Codex (and only Codex) makes the path "click Add -> click Save -> chat works" survive a single click sequence, matching the empirical setup we walked through in the e2e probe. |
||
|---|---|---|
| .. | ||
| app | ||
| assets | ||
| components | ||
| config | ||
| features | ||
| hooks | ||
| lib | ||
| shared | ||
| stores | ||
| types | ||
| utils | ||
| index.css | ||
| main.tsx | ||
| speech-recognition.d.ts | ||