Bug: pending plan questions become stuck after app restart

[marvin-bitterlich]

On v0.0.9, if T3 Code is fully closed while a thread is waiting on a plan-mode / request_user_input question, reopening the app leaves that thread stuck.

Repro

1. Start a thread that triggers a plan-mode question.
2. Close T3 Code while the question is still pending.
3. Reopen the app.
4. Return to the same thread and try to answer or continue.

Expected

The thread should recover cleanly and still allow the pending question to be answered.

Actual

The question remains visible, but the thread is effectively stuck:

• submitting answers does not work
• there is no clear way to dismiss or recover the session

Notes

This looks related to restart/resume handling for pending user-input requests. I did not find an existing open issue/PR for this exact case.

[shivamhwp]

still happening @marvin-bitterlich ??
try the latest version of the app !!

[marvin-bitterlich]

still happening @marvin-bitterlich ??
try the latest version of the app !!

I'll have a look later today, will update this (and clean up my pr if it's no longer needed)

[lucid-justin]

Experienced this on 0.0.14. This occurred after a device + app restart. Computer died with the app open. May have also contributed: codex responses failed at first due to a bad wifi connection. Plan remained frozen after that was fixed.

[shivamhwp]

still @marvin-bitterlich let me know if it's still happening!!
and @lucid-justin you let me know if this happens again!!

[lucid-justin]

@shivamhwp Confirmed that it's repeatable on 0.0.14, wifi issues did not contribute. If I continue to see it on a later version I'll update here again!

[mrinc]

0.0.15 still an issue.
Currently have a chat stuck with this bug.

https://kvyvxo3le9.ufs.sh/f/0aXhVvf6tFvSZC4MR6gcUaTB9RPNjqxs7mWKJy0gDoGCH8Vd Screen recording of it occurring.

One thing I do notice is the timer under projects is updated. (changes to 'just now')
So, it registers the action of 'submit answers'.

From what I can see in the code - https://github.com/pingdotgg/t3code/blob/main/apps/web/src/components/ChatView.tsx#L2453 Seems to be the culprit.

I think a simple fix for this without being able to debug more is to just add the ability to exit out of the user input request.
There is an issue for this already: #1479