News for hackers. Stuff that matters.
Re:GPT-5.3-Codex by fluidcruft on Thursday February 05, 2026 @06:33PM (#46906996)
That just seems like a UI difference. I've always interrupted claude code added a comment and it's continued without much issue. Otherwise if you just type the message is queued for next. There's no real reason to prefer one over the other except it sounds like codex can't queue messages?
Re:GPT-5.3-Codex by esperent on Friday February 06, 2026 @12:09AM (#46909370)
[delayed]
Re:GPT-5.3-Codex by cruffle_duffle on Friday February 06, 2026 @12:32AM (#46909477)
That is so annoying too because it basically throws away all the work the subagent did.

Another thing that annoys me is the subagents never output durable findings unless you explicitly tell their parent to prompt the subagent to “write their output to a file for later reuse” (or something like that anyway)

I have no idea how but there needs to be ways to backtrack on context while somehow also maintaining the “future context”…

Re:GPT-5.3-Codex by Skwrm on Friday February 06, 2026 @10:11AM (#46913771)
They actually made a change a few weeks ago that made subagents more steerable

When they ask approval for a tool call, press down til the selector is on "No" and press tab, then you can add any extra instructions

Re:GPT-5.3-Codex by int_19h on Friday February 06, 2026 @04:34AM (#46910812)
Codex can queue messages, but the queue only gets flushed once the agent is done with whatever it was working on, whereas Claude will read messages and adjust accordingly in the middle of whatever it is doing. It sounds like OP is saying that Codex can now do this latter bit as well.