The OGX Python SDK Has a New Foundation
Starting with ogx_client 1.1.4, the Python SDK is built on a new code generation backend. The package name and API surface stay the same — most codebases need only an import path change.
Starting with ogx_client 1.1.4, the Python SDK is built on a new code generation backend. The package name and API surface stay the same — most codebases need only an import path change.
Two weeks ago, we told you the name changed. Today, we're telling you it's done.
OGX 1.0 is a server that replaces the OpenAI API with something you own. Point your existing OpenAI, Anthropic, or Google SDK at it. Run any model on any infrastructure. Get server-side agentic orchestration, built-in RAG, MCP tool integration, multi-tenancy, and production observability out of the box. No vendor lock-in. No code changes.
This is not a beta. This is not "production-ready with caveats." This is v1.
Llama Stack is now OGX. The name changed, but more importantly, so did the mission.
When this project started, it was an API standardization effort — a set of specs for building AI applications, anchored to the Llama model family. That framing attracted contributors and integrations, but it also created confusion about what the project actually is. People thought it was a spec. Or a Llama-only thing. Or another framework.
It's none of those. OGX is a server. Specifically, it's a server-side agentic loop that speaks the native API of every major frontier lab — OpenAI, Anthropic, and Google — so your application code doesn't have to care which one you're using.
This post explains why we renamed, what changed in the project's direction, and what that means for you.
Welcome to our blog!
We're excited to introduce you to OGX - the open-source platform that simplifies building production-ready generative AI applications.