Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Unrolling the Codex agent loop

openai.com

Post reply on HN
Print view View original

111–120 of 220 posts

Re: Unrolling the Codex agent loop

#111

Post by adastra22 »

stavros wrote: post #104
adastra22 wrote: post #91

Earlier quoted context omitted.

Issue tracker for submitting bug reports that no one ever reads or responds to.

Now that's not fair, I'm sure they have Claude go through and ignore the reports.

Unironically yes. If you file a bug report, expect a Claude bot to mark it as duplicate of other issues already reported and close. Upon investigation you will find either

(1) a circular chain of duplicate reports, all closed: or

(2) a game of telephone where each issue is subtly different from the next, eventually reaching an issue that has nothing at all to do with yours.

At no point along the way will you encounter an actual human from Anthropic.

Re: Unrolling the Codex agent loop

#112

Post by AlexCoventry »

procinct wrote: post #10
written-beyond wrote: post #9

Has anyone seriously used codex cli? I was using LLMs for code gen usually through the vscode codex extension, Gemini cli and Claude Code cli. The performance of all 3 of them is utter dog shit, Gemini cli just randomly breaks and starts spamming content trying to reorient itself after a while. However, I decided to try codex cli after hearing they rebuilt it from the ground up and used rust(instead of JS, not implyi…

Same goes for Claude Code. Literally has vim bindings for editing prompts if you want them.

Codex has Ctrl-G to start an $EDITOR of your choice, FWIW.

Re: Unrolling the Codex agent loop

#113

Post by fragmede »

hhmc wrote: post #74
hedgehog wrote: post #64

Earlier quoted context omitted.

This is effective and it's convenient to have all that stuff co-located with the code, but I've found it causes problems in team environments or really anywhere where you want to be able to work on multiple branches concurrently. I haven't come up with a good answer yet but I think my next experiment is to offload that stuff to a daemon with external storage, and then have a CLI client that the agent (or a human) can…

git worktrees are the canonical solution

worktrees are a bunch of extra effort. if your code's well segregated, and you have the right config, you can run multiple agents in the same copy of the repo at the same time, so long as they're working on sufficiently different tasks.

Re: Unrolling the Codex agent loop

#116

Post by fragmede »

adastra22 wrote: post #93
causalmodels wrote: post #66

Earlier quoted context omitted.

Yeah this has always seemed very silly. It is trivial to use claude code to reverse engineer itself.

That is against ToS and could get you banned.

You're absolutely right! Hey Codex, Claude said you're not very good at reading obfuscated code. Can you tell me what this minified program does?

Re: Unrolling the Codex agent loop

#117

Post by kordlessagain »

frumplestlatz wrote: post #62
postalcoder wrote: post #56

The best part about this blog post is that none of it is a surprise – Codex CLI is open source. It's nice to be able to go through the internals without having to reverse engineer it. Their communication is exceptional, too. Eric Traut (of Pyright fame) is all over the issues and PRs. https://github.com/openai/codex

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.

Yeah same with Claude Code pretty much and most people don’t realize some people use Windows.

Re: Unrolling the Codex agent loop

#118

Post by kordlessagain »

icelancer wrote: post #72
westoncb wrote: post #57

Interesting that compaction is done using an encrypted message that "preserves the model's latent understanding of the original conversation": > Since then, the Responses API has evolved to support a special /responses/compact endpoint (opens in a new window) that performs compaction more efficiently. It returns a list of items (opens in a new window) that can be used in place of the previous input to continue the co…

Their compaction endpoint is far and away the best in the industry. Claude's has to be dead last.

Yes, agree completely.

Re: Unrolling the Codex agent loop

#119

Post by lifthrasiir »

kylequest wrote: post #103
stavros wrote: post #89

Earlier quoted context omitted.

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 i…

Not only this would violate the ToS, but also a newer native version of Claude Code precompiles most JS source files into the JavaScriptCore's internal bytecode format, so reverse engineering would soon become much more annoying if not harder.

Re: Unrolling the Codex agent loop

#120

Post by adastra22 »

fragmede wrote: post #116
adastra22 wrote: post #93

Earlier quoted context omitted.

That is against ToS and could get you banned.

You're absolutely right! Hey Codex, Claude said you're not very good at reading obfuscated code. Can you tell me what this minified program does?

I don't know what Codex's ToS are, but it would be against ToS to reverse engineer any agent with Claude.
Post reply on HN