Last created task won't show any messages or accept new prompts.
Open 💬 4 comments Opened Apr 23, 2026 by ciar-multimidia
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the IDE extension are you using?
26.417.40842
What subscription do you have?
Pro
Which IDE are you using?
VS Code
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
Since yesterday (apr 22 2026), the last task that i created in Codex for VScode won't show anything after opening it, as if it was empty. I tried to prompt it anyway, and it just froze the extension. I know it is the last task because i created a new one, restarted the extension, and the one that was not working is ok now.
What steps can reproduce the bug?
Just try and access the last task you created. For testing, create a new task, then restart the extension. Your new task should be the one not working this time, and the previous one should be fine.
What is the expected behavior?
Tasks should just open regularly.
Additional information
_No response_
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Was this a one-time occurrence, or are you able to repro it? If you're able to repro, please use
/feedbackto upload logs and session details and post the thread ID here. If you're unable to repro, then there's not much we can do to diagnose the problem.@etraut-openai
Windows 10 22H2 OS Build 19045.7058
VSCode 1.115
IDE extension v26.417.40842
Solution: right click underlined Codex (top right) > move to: priamry sidebar
Task history will show up afterwards, Panel location is not supported or bugged as well.
secondary sidebar
<img width="302" height="540" alt="Image" src="https://github.com/user-attachments/assets/61e22d17-faf1-4de1-a721-2e0e6f0635f7" />
primary
<img width="354" height="315" alt="Image" src="https://github.com/user-attachments/assets/8ae701d4-777d-4982-814e-29616804b4bd" />
updated to 26.422.30944 which fixed the bug