Fair amount of this: Error message: JSON Parse error: Unterminated string #20786

Activity

1. berenddeboer

   added

   bugSomething isn't workingSomething isn't working

   on Apr 3, 2026
2. github-actions

   assigned

   rekram1-node

   on Apr 3, 2026
3. 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 3, 2026
4. github-actions commented on Apr 3, 2026

   

   github-actionsBot

   on Apr 3, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • [BUG] openai/gpt-5.2-codex Error message: JSON Parse error: Unterminated string errors #10755: Same JSON Parse error: Unterminated string error with Codex models, same workaround (saying "continue" works)
   • Bug: Incomplete JSON stream in OpenCode using gpt-5.3-codex (Unterminated string) #20599: Same error on the same version (1.3.13) with gpt-5.3-codex during streaming

   If your issue is different, please add more details to distinguish it from these existing reports.
5. zeug-zz commented on Apr 7, 2026

   

   zeug-zz

   on Apr 7, 2026

   More actions

   I’m seeing what looks like a more specific variant of this bug on 1.3.17, and it may be related to #19405.
   In my case the failure is not just a generic:
   Error message: JSON Parse error: Unterminated string
   The leaked payload includes a raw Responses API event frame like:

   {"type":"response.created","response":{"id":"resp_...","instructions":"..."}}
   and the instructions field contains the full assembled OpenCode prompt, including:
   - system/developer instructions
   - AGENTS / repo guidance
   - skill listings
   - project-specific context
   It also appears to get contaminated by synthetic internal text, for example:
   - <system-reminder> ... Plan Mode ...
   - [MEMORY TRIGGER DETECTED]
   That makes this look like a boundary-corruption issue where:
   1. a streaming/event payload is being treated as final JSON,
   2. synthetic reminder/middleware text is getting merged into the same parse stream,
   3. the parser then dies with Unterminated string.
   So this may overlap with both:
   - this issue (#20786) for the unterminated JSON parsing failure
   - #19405 for synthetic reminder leakage into model-visible content
   The notable extra symptom here is that response.created.instructions is dumped raw, so the failure can expose a huge amount of prompt/context text instead of only failing quietly.
   This might be worth handling as:
   - do not parse response.created as final structured output
   - keep synthetic reminder/memory-trigger text out of the provider transport stream
   - redact/suppress instructions in error logging
6. thdxr

   removed

   bugSomething isn't workingSomething isn't working

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

   on May 3, 2026
7. thdxr

   assigned

   kitlangton

   and unassigned

   rekram1-node

   on May 3, 2026
8. menardorama

   added a commit that references this issue on May 3, 2026

   fix(session): use jsonrepair lib for truncated tool call JSON

   ...

   cd6d789
9. github-actions commented on Jul 3, 2026

   

   github-actionsBot

   on Jul 3, 2026 – with GitHub Actions

   Contributor

   More actions

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

    closed this as not plannedon Jul 3, 2026