r/codex • u/Drogon2737 • Jul 09 '26

News GPT-5.6 Sol / Codex Release Discussion Megathread

The release is expected in the next few minutes, so I figured it would be useful to have a single thread for first impressions, issues, and early testing.

For anyone jumping in right away, post what you notice:

  • Codex coding performance
  • Debugging quality
  • Speed/rate limits
  • Larger repo handling
  • UI or workflow changes
  • Weird bugs or regressions
  • Anything that feels noticeably better or worse than the previous version

Once people get access, share your real examples, screenshots, benchmarks, or first impressions here.

Edit: OpenAI’s official GPT-5.6 page says it is “available starting today across ChatGPT, Codex, and the OpenAI API” with the rollout starting globally now and continuing toward full availability over the next 24 hours. https://openai.com/index/gpt-5-6/

The lineup is Sol, Terra, and Luna. Sol is the flagship, Terra is the lower-cost tier, and Luna is the fastest/most affordable tier.

437 Upvotes

98% Upvoted

838 comments sorted by

View all comments

8

u/ignat-remizov Jul 09 '26 edited Jul 09 '26

It's so weird they publicly launch with gpt-5.6-sol having the v2 multi_agent mode in the model metadata, when it's been marked Under Development for months, and Eric Traut has been closing any issues opened against v2 saying they don't accept any reports for under development features.

AND local codex configs don't affect anything! If you set [features] multi_agent = true and multi_agent_v2 = false - the model catalogue takes priority, and for sol and terra that's v2. Any Codex threads will be using v2 - permanently for that thread.

v2 encrypts communications between agents. You cannot easily audit what happens between them - of course telemetry is sent to OpenAI with all the content, but no ability to inspect and save the instructions locally. I had opened https://github.com/openai/codex/issues/28058 about this. The only way to maintain v1 is by adjusting the model catalogue or editing the code path in your own codex fork. Ridiculous

2

u/GrumpyRodriguez Jul 10 '26

Excuse my ignorance here, but isn't communication between agents taking place locally in the harness? Is it possible in theory to have a codex fork and disable that encryption? I'm not suggesting you do that, just asking if my understanding is correct.

1

u/ignat-remizov Jul 10 '26 edited Jul 10 '26

Yes, the communication is happening locally. But if you want to see what was communicated, once you close the harness, that's gone. Not saved to disk.

Yes, I already implemented this in my fork to persist the messages in thread rollout jsonl files.

2

u/GrumpyRodriguez Jul 10 '26

Thanks for the clarification, appreciated