Codex weekly active users grew 400% to 5 million.
We’ve reached an agreement to acquire @ona_hq.
Its secure cloud execution technology will help Codex take on longer-running work, even when laptops are closed, and help more organizations deploy agents securely in production.
After closing, Ona will join OpenAI’s Codex team. https://openai.com/index/openai-to-acquire-ona/
Many users praised OpenAI's acquisition of Ona to enhance Codex with secure cloud execution as a solid and bullish move, while others objected that it ignores customer demands around 4o access and raises privacy concerns.
@OpenAINewsroom @ona_hq It’s a shame you don’t put this much effort into listening to your customers and giving them access to 4o. #keep4o
@OpenAINewsroom @ona_hq Why acquire when they could have Vibe Coded it themself ???
My report on confidential AI (compute) and protected tokens helps explain why this is important.
https://www.thediligencestack.com/p/confidential-ai-turning-trust-into
We’ve reached an agreement to acquire @ona_hq.
Its secure cloud execution technology will help Codex take on longer-running work, even when laptops are closed, and help more organizations deploy agents securely in production.
After closing, Ona will join OpenAI’s Codex team. https://openai.com/index/openai-to-acquire-ona/
@OpenAINewsroom @ona_hq Thank you!! OpenAI Korea B2C "ME"
@OpenAINewsroom @ona_hq The most important thing for you right now is to bring 4o back and actually listen to user feedback. #keep4o #bringback4o #opensource4o
@stark4833 @OpenAINewsroom @ona_hq
@OpenAINewsroom @ona_hq Sam Altman's own words:
Do NOT trust me.
https://m.youtube.com/watch?v=dY1VK8oHj5s
@OpenAINewsroom @ona_hq dont worry guys the open standard is coming to clanker cloud soon to do this and more
@OpenAINewsroom @ona_hq Oh hi friends
@stark4833 @OpenAINewsroom @ona_hq Dude, forget about 4o. It's outdated already and isn't even half as good as GPT-5.5"
@OpenAINewsroom @ona_hq Everyone is building agent compute. Agents also need somewhere to keep their work.
Data, memory, outputs, audit trails. Portable and verifiable.
The storage layer should be next.
@mad4synths @OpenAINewsroom @ona_hq Sorry, sorry. I’m fucked up my new language. “bi khaye morghabi kon” that should be right now. 👍🖕🏻
@OpenAINewsroom @ona_hq Long-running agents are a memory problem as much as an execution problem.
Codex with secure execution plus persistent memory is going to be a different kind of agent. 🦭
@Andrzej18212046 @OpenAINewsroom @ona_hq 4o is a lot better than 5.5 in my opinion, I find 5.5 shit and restricted as fuck.
@OpenAINewsroom @ona_hq Couldn't be more excited!
@OpenAINewsroom @ona_hq codex taking over work while the laptop is closed sounds like a dream until you wake up to a massive compute bill from an agent that went rogue overnight 💀
@stark4833 @OpenAINewsroom @ona_hq
@cute_n_clocky @NAM37 @OpenAINewsroom @ona_hq Kiram tu kunet
@stark4833 @mad4synths @OpenAINewsroom @ona_hq 🤣🤣🤣
@mad4synths @OpenAINewsroom @ona_hq Bi-khaye morghabi-kesh🖕🏻
Codex weekly active users grew 400% to 5 million.
We’ve reached an agreement to acquire @ona_hq.
Its secure cloud execution technology will help Codex take on longer-running work, even when laptops are closed, and help more organizations deploy agents securely in production.
After closing, Ona will join OpenAI’s Codex team. https://openai.com/index/openai-to-acquire-ona/
