Prompt disappears after error "Not available in app-server TUI yet for thread <thread-id-here>"
Resolved 💬 7 comments Opened Mar 29, 2026 by sanskar-tiwari-surepass Closed Apr 5, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
codex-cli 0.117.0
What subscription do you have?
Pro 200
Which model were you using?
gpt-5.4-high
What platform is your computer?
Microsoft Windows NT 10.0.19044.0 x64
What terminal emulator and version are you using (if applicable)?
Windows Terminal PowerShell
What issue are you seeing?
Prompt disappears after error "Not available in app-server TUI yet for thread <thread-id-here>"
It is not recoverable after pressing the up arrow key leading to loss of time.
What steps can reproduce the bug?
Trigger the mentioned error somehow.
One of my friend also reported loss of prompt earlier, so I am confident that this is a recurring issue.
What is the expected behavior?
On error or fail, the prompt should be recoverable.
Additional information
_No response_
7 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Not a duplicate. My issue is the loss of the prompt, not the error itself.
Thanks for reporting. This is likely a regression introduced in 0.117.0, and I'd like to get it fixed quickly. We need to first determine the steps to repro the error you're seeing.
If you're able to duplicate this, please use
/feedbackto upload your logs and session details, then post the thread ID here.Is there any additional context that might be useful in repro'ing the problem? For example, does it occur only when in
/planmode? Does it occur when subagents are running? Is there a specific prompt or skill that seems to trigger it?Due to sensitive nature of my work, I cannot upload logs. But my work was spawning lots of explorer subagents working over a very large corpus text. I was explicitly using this skill in particular https://github.com/sanskar-tiwari-surepass/codex-skills/tree/master/scratchpad
Thanks for the extra context. I think this is likely already fixed on
main.The strongest match is the stale/ghost subagent thread bug we fixed after
0.117.0in #16110, which was included starting in0.118.0. That fix prunes dead subagent entries and attaches live ones on selection instead of leaving stale/blank thread state around. Given that this repro involved lots of explorer subagents, that looks like the same underlying class of failure.I have not reproduced this exact prompt-loss path locally, so I’m calling it a likely fix rather than a guaranteed one. Could you try the latest release (or current
main) and let us know if you can still reproduce it? If yes, we should keep digging.I think this is now fixed in 0.118.0. Let me know if you see it again.