Google Engineers' Open 'Agent Executor' Orchestrator Surges on HN, Draws Branding Skepticism
A sandboxing platform for running massive fleets of AI agents, built by Google staff, jumps to the HN front page and splits commenters over how 'official' it really is.
What to know
- AX is pitched as a declarative control plane for running massive numbers of sandboxed AI agent tasks, built by Google engineers on an internal 'Agent Substrate' runtime and DeepMind agentic-runtime research.
- The project is not officially branded or confirmed as a corporate Google product; commenters note the site itself does not claim full company backing despite the HN title calling it 'Google's'.
- The launch surfaced in a crowded field of competing agent-sandboxing and orchestration tools (e.g., Mastra, an internal tool called clrk), with commenters split on whether isolated sandboxes solve a real problem or add unneeded complexity.
- No official Google statement beyond the product site accompanies the story; discussion remains confined to the Hacker News thread and its mirrors.
The dispute Whether AX represents meaningful Google institutional investment in agent infrastructure or is just another employee-built tool in an already saturated market. · positions read across 48 posts and comments
Calling this 'Google's' orchestrator overstates institutional backing; it's an employee side project, not a corporate product, and its practical value is unclear.
-
“Yes, it was developed by Google employees, that does not imply it has the full backing of Google, or Deepmind, or GCP.”
Mond_ · Hacker News ↗
The agent-orchestration space is already crowded with similar tools, so AX is one more entrant rather than something new.
-
“The agentic ecosystem is continuing to multiply on a daily basis and everyone and their grandma has written a new agent framework--people are stepping over each other to get these new projects out the door.”
briga · Hacker News ↗
AX and Google's related tooling (Antigravity, Jules, ADK) look promising and worth trying, with hope Google keeps investing in it.
-
“I have been happy with Google's Antigravity harness and Jules so looking forward to playing with this.”
mcoliver · Hacker News ↗
Google Developer of AXblazarquasar HN submitterMond_ HN commenterdilyevsky HN commenter, builder of a similar internal toolbriga HN commenter
How it unfolded 4 developments, newest first · click a bar or a number to jump articlespostscomments
-
4
HN thread debates value of agent sandboxes and rival tools
Commenters compare AX to existing frameworks such as Mastra and an internal tool called clrk, question whether isolated sandboxes are worth the complexity, and some dismiss the product page as unclear about its purpose.
“Nobody has a use for this, and anybody who can look at this website and work out what it's for is kidding themselves.”
— weedfroglozenge -
From what I've seen, the vast majority of agent sandboxes with funding aren't for developers to use when coding, but for production applications that want to have LLMs do work. It's just a different model - APIs are better than a great terminal experience for a coding harness.I've been working on https://lullabot.github.io/sandbar/latest/ which…
2 more of the top 3 · 42 posts in this stretch
-
N
AX – Google’s Open Agentic Orchestrator Link: https:// agentexecutor.io Comments: https:// news.ycombinator.com/item?id=4 9780797
-
I'm working on something in the "cloud VMs for agents" space[1], so I have some battle scars and opinions!IMO, you want the flexibility to create either: (a) permanent devbox VMs, and (b) per-task VMsAgent sandbox platforms tend to be tuned for the latter, which sometimes involves VMM hackery for fast boot, snapshotting VM filesystem and RAM…
-
-
3
Commenter Mond_ disputes calling AX 'Google's' project
A highly visible HN comment argues the tool, though built by Google employees, has not been shown to carry backing from Google, DeepMind, or GCP leadership, challenging the submission's framing.
“Yes, it was developed by Google employees, that does not imply it has the full backing of Google, or Deepmind, or GCP.”
— Mond_ -
I'd evaluated both Google's Agent Substrate (that underlies Ax) and their Scion project. I really enjoy how Scion operates with existing tools really well. Ax/Agent Substrate is much more a greenfield independent effort, it's own thing.I think Scion has so much more mature a disosition: you could write OpenCode plugins that enhance the runner, and…
2 more of the top 3 · 5 posts in this stretch
-
I really don't think any of these SOTA labs are doing agentic engineering correctly. Skills are the universal language of all agent harnesses. If you abstract the taste and prescription out of the skills and into guidance docs, then leave the skills as basically just workflow scaffolding, you can build task-specific workflows that work with any…
-
I have been happy with Google's Antigravity harness and Jules so looking forward to playing with this. Thanks for sharing. Simultaneously I am looking to also revisit local offline models.While I feel like I have a decent understanding of the model landscape I'm feeling a bit lost at which agentic harness to leverage for local models. Hermes…
-
-
2
Repost of AX launch surges to HN front page
A second submission of the same site by blazarquasar gains rapid traction, reaching 257 points and 102 comments, putting the tool in front of a much larger audience.
“AX was born at Google when agentic runtime systems research met frontier compute.”
— AX (agentexecutor.io) -
I'm not sure why, exactly. But I don't pay any attention to news like this from Google. I don't know if there's some marketing which has me writing them off or if it's something else.What I do know is that the Gemini integration into sheets is surprisingly incapable of performing basic tasks. This is where I expect Google to really shine. I…
-
-
1
AX orchestrator site first posted to Hacker News
User rochansinha submits agentexecutor.io describing AX, a Google-built declarative control plane for sandboxing and running agent tasks at scale; the post draws minimal early traction.
-
2 outlets Google's Open Agentic Orchestrator
first by HN Best, 5d ago · also HN Frontpage
-
What people are saying 17 voices from 2 sites · best of 48 · verbatim
- Is Google using AX internally for its own projects?
- Does isolating agents in sandboxes actually add enough value to justify the added complexity versus simpler VM-based setups?
- Sep 23
-
Yes perhaps easy refers to when actually using AX as a platform for deploying and managing agents, not actually installing and managing AX itself. I think it's awesome they targeted kubernetes but it's not easy from a human perspective. However with documentation and an AI assistant working with Kubernetes is so nice. I have worked with all the…
- Sep 21
-
I am confused by this. The UX of the CLI is almost identical to kubectl, but it doesn't seem to actually be built on K8s CRDs. There's a backend that runs on k8s, but doesn't seem natively integrated.Because it's using `ax apple` instead of `kubectl apply` you can't use tools like argocd for managing resources.It's built on agent substrate which…
-
I never quite understood why agents should be treated as anything but normal software engineering. "Just" build a normal service and add an async call to some agentic framework, then parse the results. There is no need to "flip" this system and have the agent BE the process and invent a whole new ecosystem to manage the complexity that this flip…
-
If you are approaching anything looking like an enterprise environment, you are likely to have Kubernetes nearby. ko is a weird requirement. ax requires agent substrate, so it makes sense that it's needed. Agent Substrate also has experimental support in kagent, so it makes sense that it is growing.I don't really like the oversubscription of agent…
-
As with everything in software engineering, any average dev can fire up a few containers with Docker, but running anything in a real environment takes a whole team of people who actually understand the platforms involved in order to deliver a fully functional service, hopefully via properly designed code (TF) for ease of reusability. Most devs…
-
So on one hand the page says> We want to make dealing with agentic infrastructure easier so you can focus on your work. AX is designed with an uncompromising focus on ergonomics, rapid iteration, and joyful workflows for both application developers and AI researchers.On the the other hand, the readme quickstart section says> You need a Kubernetes…
-
N
AX – Google’s Open Agentic Orchestrator: https:// agentexecutor.io Discussion: http:// news.ycombinator.com/item?id=4 9780797
-
We have built similar abstractions directly on top of Kubernetes [1]I was looking at this project a couple of months ago, and I did not understand why not use Kubernetes instead of rebuilding the abstractions. The reason is that Kubernetes already provides other abstractions to run services and batch job, gang scheduling, gpu and other…
-
I am wondering how this is related to https://agent-sandbox.sigs.k8s.io/ ? Since there is also
-
Yeah, my grandmother also did something on this https://github.com/nillebco/vardaEssentially there is no out of the box solution about orchestrating agents and increasing LLMs sandboxing. That's why everyone and their grandmother are re-inventing the wheel.At the same time, it's an incredibly complicated problem, with a variable perimeter (OS…
-
The general workflow I have seen for non-technical people building software is something like:- Do multiple tasks in the same context window / session, conflate different changes into the same prompt- Repo mixed with old markdown files from previous tasks, excel and word docs and 300 playwright screenshots- 5 tools all calling each other, test and…
-
For my workflow I need both, a permanent-ish VM and emphemeral sandboxes. Both have their place and pros and cons.VMs are better for personal assistant work, GUI clicktesting, investigating bugs in your personal dogfooding dev instance and anything you haven‘t yet made repeatable and fast to set up.Sandboxes are better when you need resource…
-
I have no idea, I just live in my terminal at this point, on linux. Don't use Visual Studio or Jetbrains products anymore at all. I use visual studio code to view the occasional diff and run sql queries. Other than that, zero desktop apps, just terminal & cli tooling. Its great! I have about 20 terminals open at any given time though. I have no…
- Sep 20
-
Basically everyone has a sandbox of some sort to run agents inside. Everyone has a registry of some sort for tools. Everyone has a way of running agents inside a sandbox and giving it some tools.Now the stuff people are coming up with is: how do you do authorization in this model? do you need a full sandbox all the time or can it be a workflow?…
-
> Task declares the container image and command, compute requests and limits, environment variables [...] Declares listeners the task exposes and an egress allowlist of hosts and ports the sandbox may reach. Use it to restrict an agent to, say, your LLM provider and your Git host.I'm planning to buy a whole linux mini-PC to run my agents/code…
-
I don't think there is really any convergence going on. The agentic ecosystem is continuing to multiply on a daily basis and everyone and their grandma has written a new agent framework--people are stepping over each other to get these new projects out the door.That said, I think Google's ADK ecosystem and this new AX platform is promising--I…
-
Could someone explain to me what the general workflow is now that people are converging to? I haven't really been catching up with the AI ecosystem but I was looking into agent sandboxes and VM's recently and there's a ton of these startups and tools now. Is giving the agent a temporary scratchbox really that valuable?I've been still just like…