Codex TUI's Bug Report Links Still Broken
Resolved 💬 5 comments Opened Mar 3, 2026 by doublemover Closed Mar 3, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
v107, Windows 11, Powershell 7.5.4, Pro
Was told this would be fixed in 3 days more than 3 days ago, on my reports for v105 and v106.
This is quite frustraiting. Renewed my Pro subscription for another month today thinking I'd be able to report each of the bugs I've been experiencing easily.
Is there anything at all I can do to help? I am at wits end, willing to use the tokens I pay for to do it myself. Hell, give me a pile of Windows/PS tasks, all of the worst, most obnoxious ones you don't want to do.
5 Comments
The link in the feedback flow has been fixed. Which link do you think is still broken?
If you have bugs to report, you can use this issue tracker to do so.
The
/feedbackcommand is working fine — dozens of other users are successfully using it every day.I do not think it is, I used /feedback to report a bug like I always have, clicked on the link, and it still took me to the same empty template with no information autofilled, instead of the filled out templates I had come to appreciate
I also just tried manually copy pasting and got the same empty result
OK, I'll look at it again.
But to be clear, this should not in any way prevent you from filing bugs. You can use this issue tracker directly for bugs that don't require logs or session details. And for those that do, you can create a bug and copy and paste the thread ID from the
/feedbackflow.Thank you I do appreciate it
That's a lot of extra effort for something that I pay this much for, while knowing what codex is capable of firsthand. They all require that information.
Is it unreasonable to ask for Codex to be able to handle all of this itself, asking any clarifying questions and gathering all necessary information before submitting the issue for me?
I've confirmed that the TUI bug report link was fixed, but the change didn't make it into our last release (0.107.0). It will be in 0.108.0 which should be out soon.