You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bug: pending plan questions become stuck after app restart #856
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
Start a thread that triggers a plan-mode question.
Close T3 Code while the question is still pending.
Reopen the app.
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.
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 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!
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
Activity
shivamhwp commentedon Mar 25, 2026
still happening @marvin-bitterlich ??
try the latest version of the app !!
marvin-bitterlich commentedon Mar 25, 2026
I'll have a look later today, will update this (and clean up my pr if it's no longer needed)
j-flaherty commentedon Mar 26, 2026
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 commentedon Mar 26, 2026
still @marvin-bitterlich let me know if it's still happening!!
and @lucid-justin you let me know if this happens again!!
j-flaherty commentedon Mar 26, 2026
@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 commentedon Mar 29, 2026
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
PratyushChauhan commentedon Apr 8, 2026
This is still an issue, the plan session becomes unrecoverable.
dlg0 commentedon Apr 14, 2026
still an issue in 0.0.17