### Description During session the agent would output a lengthy error ending with `Error message: JSON Parse error: Unterminated string` From share link, this item has the entire error message. Also attached the session.json to issue. <img width="291" height="109" alt="Image" src="https://github.com/user-attachments/assets/8be11751-07ef-47d3-af96-a0a71c457c79" /> [session.json](https://github.com/user-attachments/files/24871021/session.json) ### Plugins _No response_ ### OpenCode version 1.1.36 ### Steps to reproduce 1. Use `opencode` 2. Have `openai/gpt-5.2-codex` as your model 3. Use normally to plan+build 4. Randomly dumping the `Error message: JSON Parse error: Unterminated string` into the conversation 5. Say "continue" and agent picks back up 6. Error may occur again ### Screenshot and/or share link <img width="3277" height="1732" alt="Image" src="https://github.com/user-attachments/assets/6de2709c-b009-493c-b6c1-82dd99c62856" /> https://opncd.ai/share/JtdU1xX3 ### Operating System macOS 26.3 ### Terminal Warp
Activity
github-actions commentedon Jan 27, 2026
This issue might be a duplicate of existing issues. Please check:
These issues all involve JSON parsing errors during model execution. Feel free to ignore if this specific case with gpt-5.2-codex is different.
LeoNardo-LB commentedon Feb 4, 2026
Same issue
R44VC0RP commentedon Feb 4, 2026
hey @thesammykins can you run
opencode export > session.jsonon the session where you encountered that issue?thesammykins commentedon Feb 4, 2026
hey @R44VC0RP the session.json for the session is linked in my original comment :)
https://github.com/user-attachments/files/24871021/session.json
josh-burton commentedon Mar 19, 2026
Running into this constantly.
LyndseyPaxton commentedon Mar 24, 2026
I to am seeing this a lot (multiple times a day) running GPT-5.3 Codex. Not sure what additional info I can provide to help you guys diagnose this.
github-actions commentedon Jul 6, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.