opentui: fatal: undefined is not an object (evaluating 'prompt.set')

[chriswritescode-dev]

Description

TypeError: undefined is not an object (evaluating 'prompt.set')
    at <anonymous> (src/cli/cmd/tui/routes/home.tsx:120:7)
    at untrack (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:475:12)
    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 runTop (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:833:7)
    at runUserEffects (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:943:36)
    at runUpdates (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:849:17)
    at completeUpdates (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:900:17)
    at runUpdates (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:850:5)
    at setStore (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/store/dist/dev.js:221:5)...

Plugins

No response

OpenCode version

1.1.13

Steps to reproduce

shortcut / cmd to start new session from inside current session

Screenshot and/or share link

No response

Operating System

macos 15.7.3

Terminal

warp with neovim term wraped inside tmux

[github-actions]

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

• opentui: fatal: undefined is not an object (evaluating 'prompt.set') #7850: Same error, triggered by opencode --prompt "anything"
• opentui: fatal: undefined is not an object (evaluating 'prompt.set') #7818: Same error, triggered by ctrl + x + n to create new session
• opentui: fatal: undefined is not an object (evaluating 'prompt.set') #7783: Same error with identical stack trace

These all appear to be the same root cause in src/cli/cmd/tui/routes/home.tsx where prompt.set is being called on an undefined object. Feel free to ignore if your specific case differs from these reports.

[rekram1-node]

should be fixed in next release going out rn