[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
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 1-2 天
- 新手友好度
- 45/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
- Let a thread finish its turn.
- Leave that thread idle for a few hours while you keep working in other threads.
- 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).
- 主要语言
- TypeScript
- 星标
- 24.8k
- 派生
- 6.4k
- 平均合并
- 4 小时 16 分钟
- 30 天内合并 PR
- 352
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
pingdotgg/t3code 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
相似的 Issue
-
Autocomplete still accepts an option after becoming disabled可能已有人在做 @Xapollon430 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 67/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
reduxjs/react-redux#2416 · 1 条评论 ·