Unclear if Codex is working

Resolved 💬 6 comments Opened Mar 3, 2026 by danielraffel Closed May 2, 2026

💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

Codex has now been "Working (1h 10m 30s" and since there's no output in the UX it's hard to tell if it's actually doing anything. Unclear if this is a bug or just hard at work. Either way, probably worth adding some status or feedback so folks know what's going on. I can't decide whether to let it go or cancel or interrupt.

View original on GitHub ↗

6 Comments

etraut-openai contributor · 4 months ago

Can you provide more details? Which variant of Codex are you using: CLI, IDE Extension, App? Which version? Which platform?

For bug reports like this, it's useful if you use the /feedback slash command to upload your logs and session details. If you then post the thread ID in the bug report, we can investigate further.

danielraffel · 4 months ago

I am a little confused now. I literally filed /feedback and it linked me here so I assumed that everything was available to you. is that not the case?? I have no idea how to get back to it sorry. That flow was very confusing and made me assume you received everything by creating the bug. I certainly shared everything. Too bad I can't see "past" /feedback I shared so I can post here. but it's certainly associated with my Pro account which is tied to an email with the same username here @ gmail. Curious...the session doesn't appear in /resume. More reason I suppose to try to track this down if possible. Lots of weird things. Sorry I didn't realize these weren't all connected.

etraut-openai contributor · 4 months ago

Yes, I agree that the /feedback flow can be confusing. The /feedback flow uploads your logs and session details. That's sufficient for some classes of issues (like reporting undesirable model behavior), but for bugs like the one you're reporting, we need additional details and a link to the associated upload (in the form of a thread ID).

If you already used /feedback, then I just need the associated thread ID. If you're using the CLI, you can get this via /status if you have the thread loaded.

doublemover · 4 months ago

Mine did this for 3 hours yesterday, was unable to control+c or /exit. Had to force kill the process to get it to start doing anything again

lhl · 4 months ago

I am a little confused now. I literally filed /feedback and it linked me here so I assumed that everything was available to you. is that not the case?? I have no idea how to get back to it sorry. That flow was very confusing and made me assume you received everything by creating the bug. I certainly shared everything. Too bad I can't see "past" /feedback I shared so I can post here. but it's certainly associated with my Pro account which is tied to an email with the same username here @ gmail. Curious...the session doesn't appear in /resume. More reason I suppose to try to track this down if possible. Lots of weird things. Sorry I didn't realize these weren't all connected.

btw since you have an exact timestamp and codex keeps all session rollouts/traces locally you should be able to ask codex to dig out exactly what was happening. You can point it at https://github.com/lhl/vibecheck/tree/main/hackathon-stats for some session analysis code to give it a head start if you want but it can generally dig through your local ~/.codex/ JSONL directly

etraut-openai contributor · 2 months ago

This feature request hasn't received enough upvotes, so I'm closing it.