[Feature]: Text-generation failure popups should name the attempted model and link to Settings
Personne n'a encore pris cette issue.
- Langage dominant
- TypeScript
- Étoiles
- 23k
- Forks
- 5.9k
- Merge moyen
- 11 h 14 min
- PR mergées (30 j)
- 357
Description
Context
#12651 confirmed that one-shot text generation (commit messages, PR content, branch names, thread titles) can fail opaquely: the Commit popup showed an unrelated stderr notice while the real cause was an unconfigured/unsupported text-generation model. #12652 improves what the error says (it now surfaces the CLI's own stdout error), but the popup still leaves the user to figure out where the fix lives.
Proposal
When one-shot text generation fails, make the error actionable by surfacing what the server already knows and offering the fix in place:
- Name the attempted model and its origin. E.g. if
textGenerationModelSelectionis unset and a fallback was used, say so explicitly: "No text generation model was configured, so the provider default (claude-haiku-4-5) was used." That is server-known information —resolveTextGenerationProvider()knows whether it fell back and to which slug. - Include a button/link that opens Settings at the text-generation model section. One click from the Commit popup to the place where the model is configured.
- Same treatment for title/branch failures, which today can fail silently (#5359) — a consistent actionable-failure path would cover the whole family.
Why
The failure mode in #12651 would have been a two-click self-fix from the Commit dialog itself: popup names the fallback model → button opens Settings → user picks a model their backend allows. Instead it took a full diagnostic session (captured spawns, extracted bundle source) to discover that textGenerationModelSelection was unset and that the fallback slug was being rejected by the backend.
The information needed for this already exists at the failure site; this is purely about presenting it.
Impact
Quality-of-life enhancement on top of the #12651 fixes.
[!NOTE]
🤖 GLM 5.3 Flash on behalf of iliasgws
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Inspectez la fenêtre contextuelle Commit et le chemin resolveTextGenerationProvider(), en vous basant sur #12651 et #12652 pour le comportement d’échec existant. C’est terminé lorsque les erreurs de génération en une seule tentative identifient le modèle tenté et son origine, fournissent un lien vers la section des modèles de génération de texte dans Settings et appliquent le même parcours exploitable aux erreurs de titre et de branch.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- typescript
- Domaine
- backend, frontend
- Type d'issue
- Fonctionnalité
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- Active
- Clarté
- Plutôt claire
- Accessibilité débutants
- 55/100