[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

Offen
  • Stimmt etwas nicht?
#35,113 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
backend-api-design

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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).

Vorherrschende Sprache
TypeScript
Sterne
24.8k
Forks
6.4k
Ø Merge
4 Std. 16 Min.
Gemergte PRs (30 T.)
352

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus pingdotgg/t3code

Alle Issues in pingdotgg/t3code

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.