opentui: fatal: answer.join is not a function. (In 'answer.join(", ")', 'answer.join' is undefined) #4466

Open
opened 2026-02-16 17:43:51 -05:00 by yindo · 7 comments
Owner

Originally created by @aaronnodaste on GitHub (Jan 8, 2026).

Originally assigned to: @rekram1-node on GitHub.

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

Image

Operating System

No response

Terminal

No response

Originally created by @aaronnodaste on GitHub (Jan 8, 2026). Originally assigned to: @rekram1-node on GitHub. ### 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 <img width="1850" height="1422" alt="Image" src="https://github.com/user-attachments/assets/d64b5f3e-384f-4d15-a5a4-89565ce18d4c" /> ### Operating System _No response_ ### Terminal _No response_
yindo added the opentuibug labels 2026-02-16 17:43:51 -05:00
Author
Owner

@rekram1-node commented on GitHub (Jan 8, 2026):

/oc fix this bug

@rekram1-node commented on GitHub (Jan 8, 2026): /oc fix this bug
Author
Owner

@opencode-agent[bot] commented on GitHub (Jan 8, 2026):

Created PR #7394

New%20session%20-%202026-01-09T00%3A15%3A38.209Z
opencode session  |  github run

@opencode-agent[bot] commented on GitHub (Jan 8, 2026): Created PR #7394 <a href="https://opencode.ai/s/o6hJzKLt"><img width="200" alt="New%20session%20-%202026-01-09T00%3A15%3A38.209Z" src="https://social-cards.sst.dev/opencode-share/TmV3IHNlc3Npb24gLSAyMDI2LTAxLTA5VDAwOjE1OjM4LjIwOVo=.png?model=opencode/claude-opus-4-5&version=1.1.7&id=o6hJzKLt" /></a> [opencode session](https://opencode.ai/s/o6hJzKLt)&nbsp;&nbsp;|&nbsp;&nbsp;[github run](/anomalyco/opencode/actions/runs/20836473607)
Author
Owner

@vermasachin commented on GitHub (Jan 8, 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.

@vermasachin commented on GitHub (Jan 8, 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.
Author
Owner

@rekram1-node commented on GitHub (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

@rekram1-node commented on GitHub (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
Author
Owner

@damian-zajaczkowski commented on GitHub (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.

@damian-zajaczkowski commented on GitHub (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.
Author
Owner

@SnaetWarre commented on GitHub (Jan 9, 2026):

seeing this aswell!

@SnaetWarre commented on GitHub (Jan 9, 2026): seeing this aswell!
Author
Owner

@bagatka commented on GitHub (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

@bagatka commented on GitHub (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
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#4466