OpenAI News.
GPT-5.5-Cyber and the Daybreak Initiative
https://openai.com/index/gpt-5-5-with-trusted-access-for-cyber/
GPT-5.5-Cyber has been announced as part of the Daybreak initiative. The model is tailored for defensive security, including vulnerability detection, threat modeling, and code patch generation. On the CyberGym benchmark, it scored 85.6%, outperforming the base GPT-5.5 (81.8%) and Anthropic Mythos 5 (83.8%). Currently, access is restricted to verified organizations.
Codex: Rate-Limit Resets
https://community.openai.com/t/flexible-rate-limit-resets-for-codex-and-a-method-to-get-a-reset/1383470
The primary update for June 2026 is the introduction of banked rate-limit resets. How it works: if you do not exhaust your limit within a 5-hour window, the remaining portion is "banked" and saved as a separate reset to be used later. These are not API credits or monetary balances, but rather an additional limit strictly within the ChatGPT subscription. It remains valid for 30 days from the date of accrual.
Each Plus/Pro user has received one free reset, and up to three more can be earned through referrals until June 24. Some users did not see them appear until their first referral. Banked resets can be activated via the Codex desktop app under Settings → Usage remaining. Note: CLI and VS Code plugin users (as well as some Linux users) currently lack a native way to activate them and must use the desktop app. Unofficial community scripts for CLI workarounds have already emerged.
Additionally, a Codex Profile screen has been introduced, displaying usage stats and token activity graphs, which is particularly useful with the transition to token-based billing.
Codex-Maxxing: A Guide for Long-Running Sessions
https://openai.com/index/codex-maxxing-long-running-work/
OpenAI has published an official PDF guide / white paper titled Codex-Maxxing. This guide outlines how to utilize Codex as a persistent working agent handling long-term projects, rather than just answering individual queries. OpenAI envisions a future that goes beyond starting a new chat every time.
The term "Codex-maxxing" is used here to describe an approach: rather than simply asking questions, users build an entire workflow system around the agent:
- Codex can and should work with more than just code. It can control a computer, browse the web, or have MCP access to email, calendar, etc.
- Instead of separate chats, use durable workflows (Durable Threads) with accumulated project history and context compaction.
- Agent memory should be visible and isolated. Repositories store code, while a separate folder (Vault) stores context, decisions, open loops, current state of work, etc.
- Steering (guidance during execution): Instead of assigning a task and waiting for the final result, you monitor the progress in real-time and provide adjustments along the way. This interaction resembles collaborating with a human colleague: you focus on the work itself (documents, code) rather than the chat window, providing feedback on specific parts.
- Voice over text + mobile access: OpenAI believes that typed queries are often over-edited. Voice input allows users to convey emotions, raw ideas, and unstructured thoughts that modern models can process effectively. You can discuss progress with the agent on your phone while walking, while it performs tasks on your computer.
- Utilizing Heartbeats (Thread Automation): scheduled automatic checks that allow the agent to monitor repository states or CI pipelines without human intervention. The agent does not wait for a new message from the user; it returns to the task according to a schedule.
Tasks are defined by clear, verifiable exit criteria (e.g., "achieve 100% test coverage" or "reduce deployment time by 30%"), and the agent works autonomously with regular checks until they are met. A poorly formulated task is "Implement the entire plan," whereas a well-formulated one is "Port the library to Rust, keep the API compatible, and consider the task complete only when all legacy tests pass successfully."
#codex #newllmmodel