It's the logical conclusion of having as the ultimate goal vibe managing a business.

Both serve different purposes and I think it's a reasonable distinction to have between products. One is for managing your openai workspace, API, etc, the other is a consumer product. Reasonable to expect an admin to whitelist the openai cli tool but not codex

> One is for managing your openai workspace, API, etc

Well, from the page:

> openai images generate --prompt "A tiny orange robot" saves images to ~/Downloads/gpt-images/ and prints their paths, including in pipes.

That doesn't look like "managing the API". It looks like "a consumer product".

I think the real answer is Conway's Law.

Codex is interactive. This appears to be batch.

i still do not understand the critique of "vibecoded" when talking about organizations and products that are clearly LLM based.

It's a generic insult that a lot of people throw out, but when they're using the term seriously, they mean that the code doesn't get properly reviewed by a human. It probably still gets QA'd by a human, but in the final form, not reading the code.

AI-assisted generally means that a human is reviewing the code, though there's a lot of doubt about how well that can really be done with the amount of code an AI can output. It's generally capable of being as fast or faster than a human can review it.

> but when they're using the term seriously, they mean that the code doesn't get properly reviewed by a human

"vibecoded" is also a synonim for incomplete, messy, lacks cohesion, vision. In this case, I think OpenAI partially duplicates without superseding one of the CLIs with another (and same for their different chat modes... remember they had 3 not long ago).

How is the difference not obvious to you just from the name? Do you think that every CLI is an interactive agentic application? Sorry, but this is baffling.