opentui: fatal: undefined is not an object (evaluating 'input.setText')

[allisoneer]

Description

Openened this AM and got this. I've gotten it a handful of times (or something that looks similar). I normally just restart and it works the second time. Hmmm, it might happen specifically when I Try and fork an older message. e.g. when I wasn't in the chat beforehand.

Oh it could also be related to the fact that I am forking something specifically that was a slash command? And there seems to be a delay when I first open opencode and when slash commands are populated. Although I think the underlying storage of the user message (after the slash command is expanded and sent) is just the pure text after the expansion.

TypeError: undefined is not an object (evaluating 'input.setText')
    at set (src/cli/cmd/tui/component/prompt/index.tsx:412:7)
    at ref (src/cli/cmd/tui/routes/session/index.tsx:1055:21)
    at Prompt (src/cli/cmd/tui/component/prompt/index.tsx:398:9)
    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 devComponent (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:593:3)
    at <anonymous> (src/cli/cmd/tui/routes/session/index.tsx:1046:29)
    at children (src/cli/cmd/tui/routes/session/index.tsx:1068:20)
    at <anonymous> (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:1531:21)
    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 runQueue (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:904:42)
    at completeUpdates (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:860:84)
    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)...

Plugins

None

OpenCode version

0.0.0-dev-202601101658

Steps to reproduce

Idk it happens randomly I haven't observed it. And I haven't been able to replicate it yet. It seems to be something related to a freshly opened opencode. Or forking maybe.

Screenshot and/or share link

No response

Operating System

arch linux (latest probably) with wayland

Terminal

Ghostty

[github-actions]

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

• opentui: fatal: undefined is not an object (evaluating 'input.setText') #7915: opentui: fatal: undefined is not an object (evaluating 'input.setText')
• opentui: fatal: undefined is not an object (evaluating 'input.setText') #7862: opentui: fatal: undefined is not an object (evaluating 'input.setText')
• opentui: fatal: undefined is not an object (evaluating 'input.setText') #7771: opentui: fatal: undefined is not an object (evaluating 'input.setText')
• opentui: fatal: undefined is not an object (evaluating 'input.setText') #7746: opentui: fatal: undefined is not an object (evaluating 'input.setText')
• opentui: fatal: undefined is not an object (evaluating 'input.setText') #7742: opentui: fatal: undefined is not an object (evaluating 'input.setText')
• zed terminal + opencode throw input.setText error #7647: zed terminal + opencode throw input.setText error
• opentui: fatal: undefined is not an object (evaluating 'input.setText') #7634: opentui: fatal: undefined is not an object (evaluating 'input.setText')
• opentui: fatal: undefined is not an object (evaluating 'input.setText') #7633: opentui: fatal: undefined is not an object (evaluating 'input.setText')
• opentui: fatal: undefined is not an object (evaluating 'input.setText') #7619: opentui: fatal: undefined is not an object (evaluating 'input.setText')
• opentui: fatal: undefined is not an object (evaluating 'input.setText') #7581: opentui: fatal: undefined is not an object (evaluating 'input.setText')
• opentui: fatal: undefined is not an object (evaluating 'input.setText') #7541: opentui: fatal: undefined is not an object (evaluating 'input.setText')
• Broken TUI on 1.1.10 on windows terminal with git bash #7539: Broken TUI on 1.1.10 on windows terminal with git bash
• opentui: fatal: undefined is not an object (evaluating 'input.setText') #7528: opentui: fatal: undefined is not an object (evaluating 'input.setText')
• opentui: fatal: undefined is not an object (evaluating 'input.setText') #7465: opentui: fatal: undefined is not an object (evaluating 'input.setText')
• opentui: fatal: undefined is not an object (evaluating 'input.setText') #7452: opentui: fatal: undefined is not an object (evaluating 'input.setText')

All of these issues share the exact same error message originating from src/cli/cmd/tui/component/prompt/index.tsx:412 and involve operations like forking, creating new sessions, or navigating between sessions. This appears to be a widespread issue related to prompt initialization.

Feel free to ignore if none of these address your specific case.

[rekram1-node]

this was fixed make sure ur up to date

[allisoneer]

this was fixed make sure ur up to date

Thanks big dawg. But looks only partially complete via the PR #7702
Here is some AI slop that hopefully helps you fully address it:

After deep investigation, here's what I found:

The fix history is messy:

1. PR fix(tui): move props.ref to onMount #7702 (merged Jan 11) - moved props.ref to onMount to fix fork crash
2. Commit 68ed664 - REVERTED fix(tui): move props.ref to onMount #7702 because it broke --prompt flag and new session scenarios
3. PR fix: prevent prompt crash when opening new session with existing prompt #7764 (OPEN) - attempting to fix for new sessions in home.tsx
4. PR fix(tui): defer prompt.set() to prevent crash when using --prompt flag #7869 (OPEN) - attempting to fix for --prompt flag with queueMicrotask

There are TWO different bugs with the same symptom:

Bug 1: Session/Fork scenario (prompt/index.tsx + session/index.tsx)

• Status: Should be FIXED in current dev
• The current textarea ref callback approach (input = r then props.ref?.(ref)) works correctly because input is assigned before the ref is exposed
• Reasoning model confirmed: by the time ref.set() is called, input is defined

Bug 2: Home/--prompt scenario (home.tsx)

• Status: STILL BROKEN - pending PR fix: prevent prompt crash when opening new session with existing prompt #7764 or fix(tui): defer prompt.set() to prevent crash when using --prompt flag #7869
• home.tsx calls prompt.set() in onMount, but onMount can run BEFORE the child Prompt's ref callback assigns prompt
• Current code:

// home.tsx - CURRENT (broken)
let prompt: PromptRef  // undefined initially
onMount(() => {
  if (route.initialPrompt) {
    prompt.set(route.initialPrompt)  // CRASH - prompt may be undefined!
  }
})

My bug is likely Bug 2 if it happened on fresh opencode startup or when navigating to a session with initialPrompt from home. The "fork from existing session" scenario (Bug 1) should be fixed.

Question for maintainers: Are PR #7764 or #7869 going to be merged? They both try to fix Bug 2 with slightly different approaches.

---

Detailed Timeline

Date	Event	Effect
Jan 11	PR #7702 merged	Fixed fork crash by moving props.ref to onMount
Jan 11	Commit 68ed664	Reverted #7702 - broke --prompt flag
Now	PR #7764 open	Trying to fix home.tsx by calling initPrompt from ref callback too
Now	PR #7869 open	Trying to fix home.tsx with queueMicrotask

The Two Code Paths

Path A: Session fork (FIXED)

User forks message → session/index.tsx ref callback → calls r.set(route.initialPrompt)
                                                       ↓
                                                   Prompt ref callback already ran
                                                   input = r already executed
                                                   ✓ WORKS

Path B: Fresh start with initialPrompt (BROKEN)

User opens opencode → home.tsx renders → onMount fires
                                          ↓
                                      prompt.set(route.initialPrompt)
                                          ↓
                                      BUT prompt ref callback may not have run yet!
                                      ✗ CRASHES

Suggested Fix

Either merge PR #7764 or #7869, OR add a guard in PromptRef.set():

set(prompt) {
  if (!input) {
    // Buffer for later or use queueMicrotask
    queueMicrotask(() => this.set(prompt))
    return
  }
  input.setText(prompt.input)
  // ...
}