Gateway disappears from current main
Google removed AX's Gateway resource on 24 September in commit 0b5427c4. The change deletes Gateway across the API, controller, server, CLI, stores and documentation. Google's commit message says the extra resource duplicated networking already provided by Agent Substrate, creating an architectural split between the two projects.
AX v0.3.0 remains the latest tagged release. Its README still lists Task, Workspace, Gateway and Model as four first-class resources, while current main lists only Task, Workspace and Model. Main was eight commits ahead of v0.3.0 when checked on 25 September, so operators following the tag and developers building from current source now see different API shapes.
Networking moves back to Agent Substrate
Current AX documentation makes a running Agent Substrate installation an explicit prerequisite and expects AX to reach Substrate's control API inside the cluster. Removing Gateway narrows AX toward task orchestration, workspaces and model configuration while leaving the lower networking primitive to Substrate instead of maintaining an overlapping AX abstraction.
That change makes AX's pre-stable warning concrete. The project still exposes v1alpha1 resources and warns that its concepts and protocols may change before a stable release. A manifest written around the v0.3.0 Gateway resource therefore should not be assumed to survive a move to current main or a future release without changes.
Fast adoption does not settle the scale claim
GitHub showed 11,007 stars and 532 forks on 25 September, up from 4,346 stars and 190 forks recorded in Wire's 21 September update. Those figures show rapid attention around the project, but they do not establish production use or reliability.
Google continues to describe AX as designed to run billions of tasks per cluster. The repository does not publish a reproducible public load-test harness establishing that scale. The source does provide inspectable orchestration code, tests and deployment documentation, but full system validation still requires Kubernetes and a compatible Agent Substrate installation.