Commenter Mond_ disputes calling AX 'Google's' project
3 Sep 20 7:21 PM · 5d ago · 3 comments · 1 source · development 3 of 4
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_Google Developer of AXblazarquasar HN submitterMond_ HN commenterdilyevsky HN commenter, builder of a similar internal toolbriga HN commenter
The whole story articlespostscomments the bright band is this development · numbered dots are the others · click one to jump
What people said 5 voices · verbatim
-
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…
-
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…
-
The reality with releases like this is that I'm 90% sure most Google bigwigs have never heard of it, and it's misleading to label it as "Google's" in the title.Yes, it was developed by Google employees, that does not imply it has the full backing of Google, or Deepmind, or GCP. Notably, the website doesn't seem to claim this either.
-
I can understand why it was chosen, but I'm not a fan of writing a bunch of yaml.
All 4 developments of Google Engineers' Open 'Agent Executor' Orchestrator Surges… →
Hacker NewsMastodonNewswires