Codex V0.24 Discussion #2738
GeorgeWingg
started this conversation in
General
Replies: 1 comment 2 replies
-
It would be nice if there was an option to turn CoT back on as it was before, either as a command line option or maybe as a shortcut toggle. The new transcript view is a nice addition, but the previous view was nicer for following along as the model works. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Feedback on Latest Release
I have some points to discuss on the latest release and thought I would put them all here. It would be great if other people could reply with their own thoughts and feedback.
Queued Message Behavior
I think the behavior of the recently added queued message functionality is not as expected.
The behavior of the competing tool is this: all messages added to the queue are concatenated into a single request, which is then sent to the model at the next turn.
So, if I added 3 separate messages to the queue, they would be grouped into a single message sent to the model when it is next available for input.
This is useful if you have 1 queued message, and you realise you forgot to add a detail or missed something, you could add the message to the queue and it would all get sent to the model no problem.
Codex CLI, on the other hand, turns every queued message into an individual message to the model. To me this is quite a strange choice. I don’t see much purpose for this approach, and I find the concatenation of the queue into a single message to be more intuitive.
Beta Was this translation helpful? Give feedback.
All reactions