The initial version of Codex was a powerful but hard-to-adopt cloud agent. The key growth unlock was meeting developers in their existing workflows with an IDE extension. This provided an intuitive on-ramp, building trust before introducing more advanced, asynchronous delegation features.

OpenAI has quietly launched "skills" for its models, following the same open standard as Anthropic's Claude. This suggests a future where AI agent capabilities are reusable and interoperable across different platforms, making them significantly more powerful and easier to develop for.

OpenAI recommends a bifurcated approach. Startups building bleeding-edge, code-focused agents should use the specialized Codex model line, which is highly opinionated and optimized for its tool harness. Applications requiring more general capabilities and steerability across various tools should use the mainline GPT model instead.

For years, Google has integrated AI as features into existing products like Gmail. Its new "Antigravity" IDE represents a strategic pivot to building applications from the ground up around an "agent-first" principle. This suggests a future where AI is the core foundation of a product, not just an add-on.

The initial AI rush for every company to build proprietary models is over. The new winning strategy, seen with firms like Adobe, is to leverage existing product distribution by integrating multiple best-in-class third-party models, enabling faster and more powerful user experiences.

A new software paradigm, "agent-native architecture," treats AI as a core component, not an add-on. This progresses in levels: the agent can do any UI action, trigger any backend code, and finally, perform any developer task like writing and deploying new code, enabling user-driven app customization.

Using a composable, 'plug and play' architecture allows teams to build specialized AI agents faster and with less overhead than integrating a monolithic third-party tool. This approach enables the creation of lightweight, tailored solutions for niche use cases without the complexity of external API integrations, containing the entire workflow within one platform.

Instead of relying on a single, all-purpose coding agent, the most effective workflow involves using different agents for their specific strengths. For example, using the 'Friday' agent for UI tasks, 'Charlie' for code reviews, and 'Claude Code' for research and backend logic.

The developer abstraction layer is moving up from the model API to the agent. A generic interface for switching models is insufficient because it creates a 'lowest common denominator' product. Real power comes from tightly binding a specific model to an agentic loop with compute and file system access.