Repository navigation
opentui: 'prompt.set' error still occurring in v1.1.14 #8064
Description
Description
Hi! I'm still experiencing the TypeError: undefined is not an object (evaluating 'prompt.set') error on v1.1.14.
I noticed the release notes mention a fix for prompt ref initialization, but the issue seems to still occur intermittently in my setup. I'm not sure if this is a different edge case or if I'm doing something wrong.
Error Stack Trace
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 flush (src/cli/cmd/tui/context/sdk.tsx:29:7)
Environment
- OpenCode version: 1.1.14
- Operating System: macOS Sequoia
- Terminal: Ghostty (latest)
- Plugins: none
Steps to Reproduce
- Open OpenCode TUI
- Create a new session (Ctrl+X → N)
- Error occurs intermittently (not every time)
Related Issues
This seems related to #7783, #7818, #7850, #7870, #7906.
Happy to provide more information if needed. Thanks for all the great work on OpenCode!
Activity
github-actions commentedon Jan 12, 2026
This issue appears to be related to the previously closed issues you mentioned. Those issues (#7783, #7818, #7850, #7870, #7906) all reported the same 'prompt.set' error and have been closed.
Since you're still experiencing this intermittently in v1.1.14 despite the mentioned fix for prompt ref initialization, this could indicate:
Could you provide more details about:
This will help determine if this is truly a new occurrence or if the previous fix needs adjustment for your specific use case.
thdxr 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.