Getting a json parse error on the prompt history and/or token error #4277

Activity

1. ubuntupunk

   added

   bugSomething isn't workingSomething isn't working

   on Nov 13, 2025
2. github-actions

   added

   opentuiThis relates to changes in v1.0, now that opencode uses opentuiThis relates to changes in v1.0, now that opencode uses opentui

   on Nov 13, 2025
3. github-actions commented on Nov 13, 2025

   

   github-actionsBot

   on Nov 13, 2025 – with GitHub Actions

   Contributor

   More actions

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

   • opentui: fatal: undefined is not an object (evaluating 'lines().length') #4254: Fatal error with JSON/syntax parsing - same "undefined is not an object (evaluating 'lines().length')" error type
   • opentui: fatal: undefined is not an object (evaluating 'lines().length') #4178: Similar fatal error pattern after startup/config issues
   • Can't exit OpenCode when I get ConfigInvalidErrors #4246: Configuration errors preventing OpenCode from starting properly
   • do not crash on bad user config, or if we must at least provide better feedback #4145: Crash on bad user config with similar undefined object evaluation errors
   • Opencode fails to launch #4179: OpenCode fails to launch with hanging behavior

   Feel free to ignore if none of these address your specific case with prompt history JSON parse errors.
4. ubuntupunk commented on Nov 13, 2025

   

   ubuntupunk

   on Nov 13, 2025

   Last edited by ubuntupunk

   Author

   More actions

   Here is the fix:
   rm -rf ~/.local/state/opencode

   Had to grep my entire home directory to find opencode is setting state under this directory.
5. rekram1-node commented on Nov 13, 2025

   

   rekram1-node

   on Nov 13, 2025

   Contributor

   More actions

   Hm I wonder what happened
6. ubuntupunk commented on Nov 14, 2025

   

   ubuntupunk

   on Nov 14, 2025

   Author

   More actions

   Seems like a corrupted state management file caused by an unscheduled shutdown. There should be a check on the file to avoid this, before instantiating the state history?
7. rekram1-node commented on Nov 14, 2025

   

   rekram1-node

   on Nov 14, 2025

   Contributor

   More actions

   yeah I think the tui state prolly got corrupted
8. marklise commented on Nov 15, 2025

   

   marklise

   on Nov 15, 2025

   Last edited by marklise

   More actions

   @rekram1-node, I had the same situation as @ubuntupunk. In my case, the history got corrupted as the partition that opencode stores ~/.local/state/opencode/prompt-history.jsonl temporarily ran out of space. From that point forward, opencode just kept writing json into that history file so it was never going to fix itself. I simply deleted the offending json line, wrote the file, restarted and retained my prompt history and everything is back to normal.

   ❤️React with ❤️1Reacted by DavDev Yes
9. rekram1-node

   self-assigned this

   on Nov 16, 2025
10. rekram1-node

    closed this as completedin #4364on Nov 16, 2025
11. rekram1-node commented on Nov 16, 2025

    

    rekram1-node

    on Nov 16, 2025

    Last edited by rekram1-node

    Contributor

    More actions

    next release should fix both of ur issues, for whatever reason we werent capping out # of entries to that file, now it wont grow forever lol

    also introduced better error handling

    👍React with 👍2Reacted by Mark Lisé and DavDev Yes