[deleted]
Building more with GPT-5.1-Codex-Max
21–30 of 332 posts
Re: Building more with GPT-5.1-Codex-Max
#22My observation has been that Codex tends to hit logical/data-driven/back-end tasks out of the park while doing weird, random nonsense with even simple UI tasks. This could me needing to improve how I phrase my prompts, but it will be interesting to see if it's improved in that arena at all.
Re: Building more with GPT-5.1-Codex-Max
#23Somewhat related, after seeing the praise for codex in the Sonnet 4.5 release thread I gave it a go, and I must say, that CLI is much worse than Claude Code (even if the model is great, I’m not sure where the issue really lies between the two).
It was extremely slow (like, multiple times slower than Sonnet with Claude Code, though that’s partially on me for using thinking-high I guess) to finish the task, with the back-and-forths being on the order of tens of minutes.
Moreover, the context management seems to be really weird. I’m not sure how exactly it works, but - 1. It uses very little tokens / fills up the context slowly (good I guess) 2. Doesn’t seem to actually internalize the contents of files you mention to it, or it edits.
#2 here being the main one - I usually context-dump reference code for Claude Code, and it does a perfect job of adhering to codebase patterns and its architecture, while codex was completely ignorant of the existing code style.
Moreover, it wrote extremely defensive code, even for code where it wrote both ends itself.
All in all, I was really let down after seeing all the praise.
Re: Building more with GPT-5.1-Codex-Max
#24Codex CLI 0.59 got released (but has no changelog text)
Re: Building more with GPT-5.1-Codex-Max
#25Rest assured that we are better at training models than naming them ;D - New benchmark SOTAs with 77.9% on SWE-Bench-Verified, 79.9% on SWE-Lancer, and 58.1% on TerminalBench 2.0 - Natively trained to work across many hours across multiple context windows via compaction - 30% more token-efficient at the same reasoning level across many tasks Let us know what you think!
Compaction is just what Claude Code has done forever, right?
Re: Building more with GPT-5.1-Codex-Max
#26I still want something no one has, which is the ability to launch agents in different git worktrees simultaneously and check the results out on my main branch for testing when they are finished.
lots of tools that do this and I ended up going down this rabbit hole something that could just plug in to codex instead of requiring a fork
http://github.com/agentify-sh/10x
does minimal overhead with agent orchestration (its just a bash/typescript) as its main focus was adding enhancements to codex like double redundant checkpoint via git and jj (lessons learned from codex being git reset --hard happy), something like claude skills (just a bunch of mds that steer it towards specific activity like think, plan, execute), timeout wrappers (to get you unstuck if codex waits a long time), blacklist commands during yolo (rm -rf, git reset banned even if it by small chance run it) MIT licensed
you can work sequentially (subagents launch one after the other) or parallel (worktrees) but tbh sequentially is better because you understand what is going on with parallel it might be best for dealing with tests and UI.
Re: Building more with GPT-5.1-Codex-Max
#27Rest assured that we are better at training models than naming them ;D - New benchmark SOTAs with 77.9% on SWE-Bench-Verified, 79.9% on SWE-Lancer, and 58.1% on TerminalBench 2.0 - Natively trained to work across many hours across multiple context windows via compaction - 30% more token-efficient at the same reasoning level across many tasks Let us know what you think!
Compaction is just what Claude Code has done forever, right?
I am also trying to understand the difference between compaction, and what IDEs like Cursor do when they "summarize" context over long-running conversations.
Is this saying that said summarization now happens at the model level? Or are there other differences?
Re: Building more with GPT-5.1-Codex-Max
#28> Compaction enables GPT‑5.1-Codex-Max to complete tasks that would have previously failed due to context-window limits, such as complex refactors and long-running agent loops by pruning its history while preserving the most important context over long horizons. In Codex applications, GPT‑5.1-Codex-Max automatically compacts its session when it approaches its context window limit, giving it a fresh context window. It…
> due to context-window limits
context window is not some physical barrier but rather the attention just getting saturated. what did i get wrong here?
Re: Building more with GPT-5.1-Codex-Max
#29So they all release before the Nvidia numbers tonight. The real question is: How well can Nvidia hide the circular deals in the books?
Re: Building more with GPT-5.1-Codex-Max
#30I still want something no one has, which is the ability to launch agents in different git worktrees simultaneously and check the results out on my main branch for testing when they are finished.
I think I’ve described how I achieve kinda your desired workflow in a comment yesterday [0]. [0]: https://news.ycombinator.com/item?id=45970668
ha! very interesting how slept on jj is
its been essential to my workflow as well
i use both jj and git and jj is great for just creating a snapshot that i can revert to incase it fails
im still exploring it to see what else i can do with it for agentic use