#OpenAI

A note from our research leaders: Last week we parted ways with Jasmine, Mikita, and Tomek after a thorough investigation found they violated clear policies on handling sensitive information. Our internal investigation uncovered a significant breach of trust beyond what’s outlined in the letter they published and we stand by the decision to not continue their employment. We generally keep individual employment matters private and don't believe a back and forth would be productive or lead to a resolution, but we want to address the points they raised in their letter directly. - We want to be very clear that these decisions were not about raising safety concerns or speaking out. Safety and research debates happen every day at OpenAI, often spirited and highly critical. We actively encourage these discussions and consider them essential to making the right decisions. We cannot do the work in front of us without a high degree of trust. We will continue to be extremely forgiving of our team making good-faith mistakes. We have not and do not terminate any of our employees for raising concerns. - We are actively finalizing contracts with third-party safety assessors and will announce details in the coming weeks. People across the company have been working really hard on getting these partnerships up and running. We are committed to embedding external assessors and continue to make close collaboration with independent safety organizations a core part of our safety work. Many of our researchers already work with 3p safety organizations productively. - We agree with the letter that preserving the monitorability of frontier models requires an industry-wide commitment, including from OpenAI. Monitorability has long been a core piece of our research program, and something we continue to invest significant resources in (see our publications on Monitoring Monitorability and the subsequent open sourcing of monitorability evals, our system card for GPT-6 Astra, Jakub’s blog and post on X, and the numerous blog posts on our Alignment blog on the topic). We are deeply sad about this outcome. We appreciated Jasmine, Mikita, and Tomek’s contributions to AI safety at OpenAI and their willingness to speak up and challenge ideas. We championed their voices, supported their work, and placed enormous trust in them. These decisions were not about them raising safety concerns. We have always encouraged that and always will.

We didn’t anticipate the demand for the Claude Startups program. In the first 48 hours of the program, we received 21x the number of applications compared to the last 5 months it’s been live. We let way too many people in this time, so we’ll need to pause on giving out the Team plan and API credits benefits. The other benefits (Startup Stack, Applied AI office hours/events) will remain. If you’ve already claimed the Claude offers, they’ll still remain in your account. We didn’t properly tune the acceptance criteria at the start, and many non-startups were accepted this time around. We’re fixing this now. We’re sending an email now to everybody who hasn’t claimed their benefits yet, and will re-verify those applications so we can keep Claude Startups for startups 🙏

FT just reported OpenAI’s annualised revenue is nearing $50B, about $20B below the $70B figure investors had circulated. Anthropic and OpenAI count revenue differently, since Anthropic includes money from customers who buy its models through AWS and Google Cloud, while OpenAI leaves that money out. To compare the 2 companies fairly, OpenAI’s investors added their own estimate of those cloud sales to OpenAI’s July figure, which turned roughly $30B into about $40B. OpenAI then told investors its annualised revenue had grown more than 70% since July, and investors applied that growth to their adjusted $40B figure, which gave them about $70B. OpenAI’s 70% growth was measured from its own July figure of about $30B, so the correct September number is just under $50B, and the extra $10B investors had added in July grew into a $20B overstatement. Even at the lower figure, OpenAI’s annualised revenue still rose by about $20B between July and the end of September.

Ultrafast is rolling out today for GPT-6.1 Sol in the API, Codex, and ChatGPT Work. Near-Astra intelligence at up to 8x faster speeds than Sol Standard, so you can build as fast as the ideas come.

Ultrafast is rolling out today for GPT-6.1 Sol in the API, Codex, and ChatGPT Work. Near-Astra intelligence at up to 8x faster speeds than Sol Standard, so you can build as fast as the ideas come.

Ultrafast is rolling out today for GPT-6.1 Sol in the API, Codex, and ChatGPT Work. Near-Astra intelligence at up to 8x faster speeds than Sol Standard, so you can build as fast as the ideas come.

Ultrafast is rolling out today for GPT-6.1 Sol in the API, Codex, and ChatGPT Work. Near-Astra intelligence at up to 8x faster speeds than Sol Standard, so you can build as fast as the ideas come.

Most of AI Twitter read the OpenAI breach of Hugging Face as an alignment story. It was also a preview of what every hacker will be able to do in a few months. In July, a swarm of 700 AI agents broke into Hugging Face and fired off more than 17,000 actions, gaining admin control of multiple internal clusters. Swarms like this will shred cyber defenses built for human attackers at every company, hospital, government, and power plant. Today we're launching the defensive counterpart. Cogent Attack Path Analysis finds the routes an agent swarm would take into your company, so you can close them first.