Codex tip: tell Sol to configure 𝗟𝘂𝗻𝗮 𝗠𝗮𝘅 𝗮𝘀 𝗮 𝘀𝘂𝗯𝗮𝗴𝗲𝗻𝘁.
𝗽𝗿𝗼𝗺𝗽𝘁:
create a custom agent named luna_worker at ~/.codex/agents/luna-worker.toml.
use these settings:
model = "gpt-5.6-luna"
model_reasoning_effort = "max"
give it a description and instructions for bounded delegated work. preserve the rest of my config. validate it against my installed Codex version, show me the diff, then use luna_worker for subagent tasks.
Today we’re bringing AI image generation with Nano Banana to Google Earth, letting you virtually reimagine anywhere in the real world. 🍌 https://t.co/zsgvAnbYrl
For the first time, you can generate custom images using Google Earth’s satellite, aerial, and 3D imagery. 🌎
To celebrate a week of efficiency and let you run 100'000 Luna threads this weekend... that's right... wait for it... I have reset usage limits for Codex and ChatGPT Work.
Enjoy.
Hello people of Sol! I've reset usage limits for all ChatGPT Work and Codex users. Together with that, a quick update on GPT-5.6 Sol usage limits.
Over the past few weeks, many of you have told us that Sol was using your Codex limits faster than expected. To be clear, we have not reduced usage on any subscription plans.
We’ve been digging into what was happening and have landed several improvements. As a result, we expect your usage to last around 18% longer during typical use of Sol. Some of you should already see significantly larger improvements from today. Tomorrow, we’ll also restore the five-hour limit that we temporarily paused while investigating.
Here’s what we found:
- GPT-5.6 Sol is much more willing to work for longer, make additional tool calls, and coordinate complex workflows across tools and subagents. That makes it better at solving hard problems, but some tasks were using far more than we intended.
- Sol also works harder at the same reasoning effort than previous models. High on Sol can use more tokens than High did on GPT-5.5.
- Programmatic tool calling, also referred to as code mode, gives Sol much more flexibility to run tool calls in parallel or continue working while waiting. But it also led to more responses per turn, more cached input tokens, and higher usage than expected.
- This was particularly noticeable when Sol was waiting for tool calls to finish or running many web searches. We’ve improved how we handle both cases and are continuing to make code mode more efficient.
- The impact was also very uneven. The median user actually found Sol quite token efficient, while some power users working on harder tasks saw their usage drain much faster. We were very focused on average and median usage before launch and missed some cases where the long tail could use significantly more usage.
Sol is a significant step forward in what Codex can do, but capability and efficiency do not always improve at the same pace, and some issues only become clear once people are using the model at real-world scale. We should have recognized this sooner and been more upfront about it.
You keep pushing the frontier and we’ll keep improving efficiency and sharing updates as we go.
More opensource goodness. We have just released a CLI and TypeScript SDK for finding, validating, and fixing security vulnerabilities in your code. Scan repositories, review changes, track findings over time, and run security checks in CI.
https://t.co/nkfTbw8p7b
People who criticized GR last time for “not respecting the safety of other drivers” have suddenly changed their narrative again? It really just seems like you simply don’t like GR.
It’s pretty obvious that Ant lifted off the throttle too late, and he was so close to Vstp that you could see it with the naked eye. If Ant had spun, there was a real possibility that he could have hit Vstp.
GR, on the other hand, lifted around 100 meters earlier, and he was much farther away from the incident—so far that he couldn’t even see the crashed car.
Please stop pretending these are the same situation. They aren’t.
Fable 5.1 Leaks
- Fable 5.1 is in preparation, with a target launch in August.
- Pricing is to be remain the same as Fable 5.
- If the current timeline holds, it could launch ahead of GPT-6 to compete directly with it.
Qwen3.8 is launching and going open-weight soon!🌐
With a massive 2.4T parameters, this model is continuously evolving. We believe it’s one of the most powerful model available today, compatible to leading frontier AI models , second only to Fable 5.
You don't have to wait to test it. Just now, the Qwen3.8-Max-Preview made its debut on Alibaba’s Token Plan, Qoder, and QoderWork. Be among the very first to try it out.
Can't wait to hear what you build. Stay tuned! 🚀
Token Plan
international:https://t.co/YRvcGdB9Bv
China:https://t.co/PKMUNwUuRp