Repository navigation
opentui: fatal: answer.join is not a function. (In 'answer.join(", ")', 'answer.join' is undefined) #7392
Closed as not planned
Description
Description
TypeError: answer.join is not a function. (In 'answer.join(", ")', 'answer.join' is undefined)
at format4 (src/cli/cmd/tui/routes/session/index.tsx:2633:19)
at <anonymous> (../../node_modules/.bun/@opentui+solid@0.1.70+897ebc1644d3edd0/node_modules/@opentui/solid/index.js:148:62)
at runComputation (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:742:22)
at updateComputation (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:724:3)
at createRenderEffect (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:240:75)
at insert (../../node_modules/.bun/@opentui+solid@0.1.70+897ebc1644d3edd0/node_modules/@opentui/solid/index.js:148:5)
at <anonymous> (src/cli/cmd/tui/routes/session/index.tsx:2662:19)
at createRoot (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:203:12)
at <anonymous> (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:1173:23)
at untrack (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:475:12)...
Plugins
No response
OpenCode version
1.1.8
Steps to reproduce
Not sure - I had exited out after 1.1.8 update and then used ^x+l to select another session and as soon as I selected the session it failed.
Screenshot and/or share link
Operating System
No response
Terminal
No response
Metadata
Metadata
Assignees
Labels
No labels
Activity
rekram1-node commentedon Jan 9, 2026
/oc fix this bug
opencode-agent commentedon Jan 9, 2026
Created PR #7394
opencode session | github run
vermasachin commentedon Jan 9, 2026
I got the same error, but only when opening some of my sessions created today (probably created before 1.1.8). New sessions created after 1.1.8 work for me and older sessions from few days back also open without this error.
rekram1-node commentedon Jan 9, 2026
I think this was due to a breaking change in answer question tool outputs, I think there was a case an invalid answer could appear which caused these issues and broke a lot of type assumptions (that are now reasonable).
I doubt this will impact many people tbh since it isnt possible going forward, only certain old sessions w/ invalid data will have it
damian-zajaczkowski commentedon Jan 9, 2026
I experienced a similar issue with version 1.1.8. I "resolved" it by disabling autoupdate in the opencode.json configuration file (by adding "autoupdate": false) and installing version 1.1.7, which works without the fatal error.
SnaetWarre commentedon Jan 9, 2026
seeing this aswell!
bagatka commentedon Jan 9, 2026
@rekram1-node Would it make sense to add this as a temporary backward compatibility fix and keep it for a couple of weeks while most users migrate to the new answer schema? This would prevent old sessions from becoming unusable. We could remove it later once the transition period is over.
Just in case, add fix there to work with my old sessions: #7470
github-actions commentedon Mar 25, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.