Unanswered question disappears from UI after OpenCode restart

[aklajnert]

Description

When restarting OpenCode with an unanswered question in the session, reopening the same session no longer shows that question in the UI (both GUI and TUI). I can still see in the context that the last message was a question, but the visible conversation omits it, so I cannot continue answering it directly.

Expected behavior:
The unanswered question should still be visible in the conversation UI so I can answer it and continue the tool flow.

Actual behavior:
The last question is present in the context, but it is not rendered in the UI/TUI, so I cannot answer it and must send a new prompt referencing the original question.

Why it matters:
For GitHub Copilot, answering via the question tool does not consume a premium request, but sending a new prompt does, so this bug forces unnecessary extra premium usage.

Plugins

none

OpenCode version

v1.2.14

Steps to reproduce

1. Create a new session, use a prompt like: "Ask me a question using question tool"
2. Restart opencode without answering the question
3. Go back to the same session

Screenshot and/or share link

You can see that the question is there, just not shown by OpenCode:

Operating System

Windows 11

Terminal

Windows Terminal

[andreigiura]

I have encoutered the same problem using kimi k2.5.

[axsuul]

ran into this too. dug into the code and here's what's happening:

the pending question state lives entirely in-memory as Promise resolve/reject callbacks in question/index.ts. when the process restarts, that map is gone. worse, the processor cleanup loop (processor.ts:378-394) actively marks any running/pending tool parts as error: "Tool execution aborted", so the question ToolPart gets overwritten before anyone can recover it.

the thing is, the ToolPart on disk does contain the full question input (questions, options, headers) in state.input while it's in running status. so all the info needed to re-show the question is already persisted, it just gets destroyed on cleanup and nobody tries to restore it.

[aklajnert]

I have already created a PR for this (#15603) , but it got buried in the queue.

[tredondo]

Just ran into this in 1.2.24. Hope your PR gets reviewer @aklajnert .