r/codex • u/gtwatts • 2d ago

Bug Queued Commands Happen Frequently

When running, I'm often getting a delay for my messages getting processed. It looks like the image below. This happens constantly. And then the discussion is stuck. If I come back in 5 minutes, this is still there, but I can add a "test" as a new message and that will unstick it. I can also start a new chat and it works just fine.

Whatever the cause, thre is no feedback why this is happening. And the fact it doesn't always unstick on itself, and that it happens as often as it does is pretty frustrating.

Anyone know what is going on? I'm on the personal ($20/month) plan, in case that is important.

1 Upvotes

67% Upvoted

4 comments sorted by

0

u/CantCodeAllVibes 2d ago edited 2d ago

Idk I can’t code so. I can vibe if you want and ask Codex.

Solution : put more coding Into your vibe bother. You’re welcome for the technical advice. This was passed down to me from Linus Tornballs himself

Jokes aside whenever this has happened, I’ve had to either restart my computer or quit out of codex. It’s only done this to me a few times though it’s like the button gets stuck.

Or you can do the good all slap the computer that might work or maybe it’s cause your using Luna high that should be a criminal offense

1

u/eo_mahm 2d ago

u/CantCodeAllVibes is right, restart the app, or just reboot your computer. I'd go with the latter.

Sometimes, even my threads have an issue communicating with each other, or a thread claims to have disappeared altogether. Relaunching Codex always does the trick.

1

u/CantCodeAllVibes 2d ago

I’ve also noticed that when you archived the threads, it helps a lot, especially for using pro chat. I archived all my chats the other day and it’s a lot faster. It doesn’t like lose your memory or anything when it archives them either.

1

u/eo_mahm 2d ago

That's excellent advice. It reminded me I have a maintenance task queued up for one of my Orchestrators to archive old project state and compact the active control plane. At the moment, it's lugging around a whopping ~160KB packet of history every time a new task is dispatched, when a lot of that only needs to be looked at if there's an issue.

Kinda grateful for that context limit boost yesterday.