You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Error Writing Large Files (at least with Kimi K2.5) #10967
I also encountered the same issue. I was working on Agent Skill yesterday and today. Yesterday it was completely correct, but today it failed.
The SKILL I was using involved generating JSON, HTML, and escape characters, and the same problem occurred with the write component.
I was using the Windows platform, with LLM being Claude Opus 4.5 and Minimax M2.1.
Just now, I removed OpenCode and Desktop for version 1.1.39. After reverting to version 1.1.36, there were no abnormalities.
Therefore, the temporary solution is to revert to version 1.1.36.
I am currently attempting to analyze and review the updates from 1.1.37 to 1.1.39.
Thank you to the developers for their work.
Reacted by Yifan Xiong and Chindriș Mihai - Alexandru
I think equally frustrating is that when you encounter this issue with Kimi K2.5, the agent just stops instead of retrying or continuing the task with a different approach, like in typical tool failures. And if it is in a subagent and the subagent fails, you often have to scrap the whole run, because you cannot simply ask it to continue.
Activity
github-actions commentedon Jan 28, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
ideallove commentedon Jan 28, 2026
I also encountered the same issue. I was working on Agent Skill yesterday and today. Yesterday it was completely correct, but today it failed.
The SKILL I was using involved generating JSON, HTML, and escape characters, and the same problem occurred with the write component.
I was using the Windows platform, with LLM being Claude Opus 4.5 and Minimax M2.1.
Just now, I removed OpenCode and Desktop for version 1.1.39. After reverting to version 1.1.36, there were no abnormalities.
Therefore, the temporary solution is to revert to version 1.1.36.
I am currently attempting to analyze and review the updates from 1.1.37 to 1.1.39.
Thank you to the developers for their work.
ideallove commentedon Jan 28, 2026
@marcoschwartz I have fixed the problem I encountered. Maybe your problem has also been resolved.
Mithrillion commentedon Jan 28, 2026
I think equally frustrating is that when you encounter this issue with Kimi K2.5, the agent just stops instead of retrying or continuing the task with a different approach, like in typical tool failures. And if it is in a subagent and the subagent fails, you often have to scrap the whole run, because you cannot simply ask it to continue.
ideallove commentedon Jan 29, 2026
Why This Causes invalid Tool Errors?
It is more likely to trigger in the subagent. In conclusion, hardcoding will definitely cause problems.
Apart from reverting to the previous version, adding a detection for JSON parsing might make the system more stable.