Earlier quoted context omitted.
OpenCode is amazing, though.
Especially that RCE!
A new one or one previously patched?
Unrolling the Codex agent loop
101–110 of 220 posts
Re: Unrolling the Codex agent loop
#102One thing that surprised me when diving into the Codex internals was that the reasoning tokens persist during the agent tool call loop, but are discarded after every user turn. This helps preserve context over many turns, but it can also mean some context is lost between two related user turns. A strategy that's helped me here, is having the model write progress updates (along with general plans/specs/debug/etc.) to…
where do you save the progress updates in? and do you delete them afterwards or do you have like 100+ progress updates each time you have claude or codex implement a feature or change?
Re: Unrolling the Codex agent loop
#103Earlier quoted context omitted.
For some reason a lot of people are unaware that Claude Code is proprietary.
Can't really fault them when this exists: https://github.com/anthropics/claude-code
By the way, I reversed engineered the Claude Code binary and started sharing different code snippets (on twitter/bluesky/mastadon/threads). There's a lot of code there, so I'm looking for requests in terms of what part of the code to share and analyze what it's doing. One of the requests I got was about the LSP functionality in CC. Anything else you would find interesting to explore there?
I'll post the whole thing in a Github repo too at some point, but it's taking a while to prettify the code, so it looks more natural :-)
Re: Unrolling the Codex agent loop
#104Re: Unrolling the Codex agent loop
#105Earlier quoted context omitted.
At this point I just assume Claude Code isn't OSS out of embarrassment for how poor the code actually is. I've got a $200/mo claude subscription I'm about to cancel out of frustration with just how consistently broken, slow, and annoying to use the claude CLI is.
Anthropic/Claude's entire UX is the worst among the bunch
What’s the best?
Re: Unrolling the Codex agent loop
#106Earlier quoted context omitted.
I appreciate the sentiment but I’m giving OpenAI 0 credit for anything open source, given their founding charter and how readily it was abandoned when it became clear the work could be financially exploited.
I agree that openAI should be held with a certain degree of contempt, but refusing to acknowledge anything positive they do is an interesting perspective. Why insist on a one dimensional view? It’s like a fraudster giving to charity, they can be praiseworthy in some respect while being overall contemptible, no?
Why even acknowledge them in any regard? Put trash where it belongs.
Re: Unrolling the Codex agent loop
#107Earlier quoted context omitted.
That is against ToS and could get you banned.
GenAI was built on an original sin of mass copyright infringement that Aaron Swartz could only have dreamed of. Those who live in glass houses shouldn't throw stones, and Anthropic may very well get screwed HARD in a lawsuit against them from someone they banned. Unironically, the ToS of most of these AI companies should be, and hopefully is legally unenforceable.
Are you volunteering? Look, people should be aware that bans are being handed out for this, lest they discover it the hard way.
If you want to make this your cause and incur the legal fees and lost productivity, be my guest.
Re: Unrolling the Codex agent loop
#108I use 2 cli - Codex and Amp. Almost every time I need a quick change, Amp finishes the task in the time it takes Codex to build context. I think it’s got a lot to do with the system prompt and a the “read loop” as well, amp would read multiple files in one go and get to the task, but codex would crawl the files almost one by one. Anyone noticed this?
Amp uses Gemini 3 Flash to explore code first. That's model is a great speed/intelligence trade-off especially for that use case.
Re: Unrolling the Codex agent loop
#109I use 2 cli - Codex and Amp. Almost every time I need a quick change, Amp finishes the task in the time it takes Codex to build context. I think it’s got a lot to do with the system prompt and a the “read loop” as well, amp would read multiple files in one go and get to the task, but codex would crawl the files almost one by one. Anyone noticed this?
Which Gpt model and reasoning level did you use in Codex and Amp? Generally I have noticed Gpt 5.2 codex is slower compared to Sonnet 4.5 in Claude Code.
Amp doesn't have a conventional model selector - you choose fast vs smart (I think that's what it is called).
In smart mode it explores with Gemini Flash and writes with Opus.
Opus is roughly the same speed as Codex, depending on thinking settings.
Re: Unrolling the Codex agent loop
#110Earlier quoted context omitted.
OpenCode also has an extremely fast and reliable UI compared to the other CLIs. I’ve been using Codex more lately since I’m cancelling my Claude Pro plan and it’s solid but haven’t spent nearly as much time compared to Claude Code or Gemini CLI yet. But tbh OpenAI openly supporting OpenCode is the bigger draw for me on the plan but do want to spend more time with native Codex as a base of comparison against OpenCode…
Seconded. I find codex lacks only two things: - hooks (this is a big one) - better UI to show me what changes are going to be made. the second one makes a huge diff and it's the main reason I stopped using opencode (lots of other reasons too). in CC, I am shown a nice diff that I can approve/reject. in codex, the AI makes lots of changes but doesn't pin point what changes it's doing or going to make.
I think Codex is probably marginally stronger than Opus in my testing.
But it's much much worse at writing issues than Claude models.