[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

Abierto
  • ¿Algo no está bien?
#35,113 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend-api-design

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
TypeScript
Estrellas
24.8k
Forks
6.4k
Merge medio
4 h 16 min
PR fusionados (30 d)
352

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de pingdotgg/t3code

Todos los issues de pingdotgg/t3code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.