JSON parsing errors in tool call arguments #23065

Activity

1. github-actions

   assigned

   rekram1-node

   on Apr 17, 2026
2. github-actions

   added

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   on Apr 17, 2026
3. github-actions commented on Apr 17, 2026

   

   github-actionsBot

   on Apr 17, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue doesn't fully meet our contributing guidelines.

   What needs to be fixed:

   • No issue template was used. Please use one of the three required templates: Bug Report, Feature Request, or Question.
   • The description lacks required fields: no reproduction steps, no environment/system information, and no details about what was expected vs. what actually happened.
   • Bug reports should include context on how to reproduce the issue (OpenCode version, provider, model, steps to reproduce, etc.).

   Please edit this issue to address the above within 2 hours, or it will be automatically closed.

   ---

   This issue might be a duplicate of existing issues. Please check:

   • Tool call arguments may contain invalid JSON #17750: Tool call arguments may contain invalid JSON — same root cause (LLM-generated malformed/truncated JSON in tool call arguments, same error message pattern)
   • retry invalid tool-call diff / malformed tool input instead of aborting #15906: retry invalid tool-call diff / malformed tool input instead of aborting — covers the same JSON parsing failed error and proposes retry/repair behavior
   • Truncated tool calls are misclassified and unrecoverable (finishReason: length + repairToolCall + doom loop) #18108: Truncated tool calls are misclassified and unrecoverable — related issue about handling truncated/malformed tool call responses

   If you believe this was flagged incorrectly, please let a maintainer know.
4. github-actions

   added

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Apr 17, 2026
5. github-actions commented on Apr 17, 2026

   

   github-actionsBot

   on Apr 17, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

   Feel free to open a new issue that follows our issue templates.
6. github-actions

   removed

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Apr 17, 2026
7. github-actions

   closed this as not plannedon Apr 17, 2026