GLM 4.7 AI_JSONParseError #8431

Activity

1. Wierzciu

   added

   bugSomething isn't workingSomething isn't working

   on Jan 14, 2026
2. github-actions

   assigned

   rekram1-node

   on Jan 14, 2026
3. Wierzciu

   changed the title [-]GLM 4.7[/-] [+]GLM 4.7 AI_JSONParseError[/+] on Jan 14, 2026
4. github-actions

   added

   zenRelates to ZenRelates to Zen

   on Jan 14, 2026
5. github-actions commented on Jan 14, 2026

   

   github-actionsBot

   on Jan 14, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • [Bug] JSON Parse Error with Zhipu GLM-4.7: Stream chunks are concatenated incorrectly #7692: [Bug] JSON Parse Error with Zhipu GLM-4.7: Stream chunks are concatenated incorrectly
   • SSE streaming parse error with GLM-4.7 responses #8282: SSE streaming parse error with GLM-4.7 responses
   • GLM-4.7 often get stuck in thinking #8428: GLM-4.7 often get stuck in thinking
   • 🐛 Bug Report: MCP Tool JSON Parsing Errors on OpenCode (GLM-4.7) #8102: 🐛 Bug Report: MCP Tool JSON Parsing Errors on OpenCode (GLM-4.7)

   All of these issues report similar JSON parsing errors and streaming issues with the GLM-4.7 model. The root cause appears to be related to how SSE (Server-Sent Events) chunks are being parsed and handled during streaming responses from GLM-4.7.

   Feel free to ignore if your specific case differs from these issues.
6. Wierzciu commented on Jan 15, 2026

   

   Wierzciu

   on Jan 15, 2026

   Author

   More actions

   
7. github-actions commented on Mar 26, 2026

   

   github-actionsBot

   on Mar 26, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
8. github-actions

   closed this as completedon Mar 26, 2026