r/OpenaiCodex • • 23h ago

Discussion Bench and feedbacks are brutal for 6.2

7 Upvotes

What couldn't be done in the mighty 28 days couldn't be done in months as well. I wanted codex to win but it's not looking good. Though it really seems they are targetting more general use rather than letting people build with and burn gazillions token.


r/OpenaiCodex • • 13h ago

News Your AGENTS.md shapes code security more than your model choice, according to a 30-model benchmark where curated rules cut risk by up to 70%

Thumbnail
leaddev.com
1 Upvotes

AI coding rules matter more than your model.


r/OpenaiCodex • • 18h ago

Usage resets no longer offered

10 Upvotes

I used to be able to buy a reset for my 7 day usage limit. Starting today that option no longer appears. Does anyone know if this is intentional or has something to do with the new model that was released? I did try asking the support AI but it just told me that not everyone is eligible for buying usage resets... But yesterday I could...


r/OpenaiCodex • • 15h ago

Discussion I been using 6.2 Sol for different roles with specific focus areas - Its bonkers on efficiency and time for completion.

7 Upvotes

I been using 6.2 Sol on high, xhigh and max reasoning for a complex backend work.

6.1 Terra (max) is the orchestrator and it spinned 15 sessions of which 9 are 6.2 Sol sessions. The first thing I observed is how fast and efficient 6.2 Sol is compared to 6.1 Terra (max)

Below image is where I am using 6.1 Terra (max) and 6.2 Sol (max) for review of same set of changes and spinned them in same time. In fact, I took 2 rounds of reviews for 6.2 Sol (max) and only one round for 6.1 Terra (max).

Just focus here on the Tokens and Speed for completion. 6.2 Sol is a beast, a monster on token efficiency and completion time.

6.1 Terra (max) spent 121 Million and took 53 minutes for 1 round.

6.2 Sol (max) spent 21 Million and 25 minutes for 2 rounds.

6.2 Sol (max) vs 6.1 Terra (max)
Overall
roles
breakdown

r/OpenaiCodex • • 21h ago

Is your coding agent managing you? How do you decide what it can settle without asking?

3 Upvotes

A post in r/ClaudeCode this week put a name on something. The agent keeps "presenting me with decision cards", and it feels like "instead of me controlling the coding agent, it starts to control me". The fix they want: "agents digest MY context and implement it with sufficient authority to prevent these unnecessary escalation."

Two replies stuck with me. One: "Anything reversible inside the task, the agent decides and writes it down in a short log. Anything touching requirements, new deps, schema or deleting stuff, it stops and asks." The other: "A question that doesn't carry its own context isn't worth answering."

For people running Codex (or Claude Code, Cursor) on real projects:

  • What does your agent decide on its own, and what has to come back to you?
  • Where do the decisions it made alone get written down, and does the next session read them?
  • How many of its questions could it have answered if it knew what you'd already decided?
  • What are you building, and with which tools? (I'm collecting real workflows to test against.)

Background: I used to burn hours re-briefing AI tools, and I'm building a fix: project decisions kept in the cloud that any coding tool reads over MCP at the start of a session and saves to at the end. No name, no link. Would you pay for that, or does a decisions log in the repo do it?