[Bug]: First message with an image or skill fails with "provider could not start this turn" after a thread sits idle for a few hours

Ouverte
  • Quelque chose ne va pas ?
#35,113 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
1-2 jours
Accessibilité débutants
45/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
typescript
Domaine
backend-api-design

Piste de recherche

Start in the apps/server area named in the issue and trace how a thread resumes after sitting idle, focusing on first messages that include an image or skill reference. Compare that path with a plain-text first message and inspect the server logs or provider setup when available. Done when the affected first message starts normally after the idle period and retries are no longer needed.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/server

Steps to reproduce
  1. Let a thread finish its turn.
  2. Leave that thread idle for a few hours while you keep working in other threads.
  3. Come back to it and send a first message that has an image attached or references a skill (e.g. /unslop).
Expected behavior

The turn starts normally.

Actual behavior

The turn never starts and I get:

Provider error
The provider could not start this turn. Retry the turn; if it keeps failing, check the provider setup and server logs.

Retrying gives the same error. I also tried editing the message to replace /unslop with plain text "unslop skill", and that still failed, so it's not only the skill reference itself.

If I send the same message without the image or skill, it works. After that, images and skills work fine in that thread again.

Impact

Minor bug or occasional failure

Version or commit

0.1.10 nightly (build from around 2026-11-11)

Environment

macOS, desktop app, Claude Code provider

Logs or stack traces
Didn't grab server logs from the machine this happened on. I can try to capture them next time it reproduces.
Workaround

Send a plain-text message first, then send the one with the image or skill.

Possibly related: #20828 (same generic error with the underlying cause dropped).

Langage dominant
TypeScript
Étoiles
24.8k
Forks
6.4k
Merge moyen
4 h 16 min
PR mergées (30 j)
352

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de pingdotgg/t3code

Toutes les issues de pingdotgg/t3code

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.