opentui: crash #3462

Activity

1. rekram1-node

   assigned

   thdxr

   on Oct 26, 2025
2. rekram1-node

   added

   bugSomething isn't workingSomething isn't working

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

   on Oct 26, 2025
3. rekram1-node commented on Oct 26, 2025

   

   rekram1-node

   on Oct 26, 2025

   ContributorAuthor

   More actions

   This happened because of an invalid agent definition, if I run old opencode it will give a better error:

   bun x opencode-ai@latest
   Error: Config file at /Users/aidencline/development/opencode2/.opencode/agent/docs.md is invalid
   
4. github-actions commented on Oct 26, 2025

   

   github-actionsBot

   on Oct 26, 2025 – with GitHub Actions

   Contributor

   More actions

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

   • Collected Feedback for OPENTUI #3232: Similar FATAL ERROR with TypeError evaluating undefined objects in opentui - shows "undefined is not an object (evaluating 'store.prompt.input')" which is very similar to your "undefined is not an object (evaluating 'x3.data.providers')" error
   • opentui: No input history -> Up arrow crashes the app #3414: Another opentui crash on startup issue when pressing arrow keys on fresh installation

   Feel free to ignore if none of these address your specific case.
5. veracioux commented on Oct 26, 2025

   

   veracioux

   on Oct 26, 2025

   Contributor

   More actions

   I think to fully address this issue, we need to do a thorough implementation of proper error handling in sync.tsx. For one, #3447 fixes this for invalid model in an agent *.md file (e.g. if you specify model: 1)

   If you want you can offload this task to me - I can tackle it tomorrow.
6. rekram1-node commented on Oct 27, 2025

   

   rekram1-node

   on Oct 27, 2025

   ContributorAuthor

   More actions

   @veracioux should it be handled in sync.tsx? I would think that a validation error for invalid config should stop before it even spawns the tui
7. veracioux commented on Oct 27, 2025

   

   veracioux

   on Oct 27, 2025

   Contributor

   More actions

   @rekram1-node That's a good point for this case, but I was talking more generally. For example, I see a lot of ! assertions in sync.tsx that seem fragile to me. That's why I suggest a proactive approach instead of a diagnostic approach.
   But yes, I agree, this proactive approach should not be confined to just sync.tsx.
8. rekram1-node

   closed this as completedon Jan 20, 2026