[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

Aberta
  • Algo errado?
#35,113 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
45/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
typescript
Domínio
backend-api-design

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
TypeScript
Estrelas
24.8k
Forks
6.4k
Merge médio
4h 16min
PRs com merge (30d)
352

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de pingdotgg/t3code

Todas as issues de pingdotgg/t3code

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.