logoalt Hacker News

AX – Google’s Open Agentic Orchestrator

628 pointsby blazarquasaryesterday at 10:32 PM288 commentsview on HN

Comments

Lethalmantoday at 5:59 AM

How is this different than k8s jobs?

show 1 reply
iamgopaltoday at 8:38 AM

Kubernetes but for agent ?

pelorattoday at 9:10 AM

It's crazy how far behind Google has fallen in this space in just a single year

yangyemotoday at 5:53 AM

It looks great from a security standpoint, but it also feels like overkill.

yash-sri19today at 6:06 AM

not exactly for agent orchestrator, but I did make something similar in terms of design: https://github.com/yash-srivastava19/cadence

jonahtoday at 3:42 AM

AX, not to be confused with Ax the machine learning tool from Meta for optimizing experiments.

https://ax.dev

show 1 reply
Mizzayesterday at 10:59 PM

k8sification of AI was always inevitable, if only as a form of salary justification.

show 1 reply
frangonftoday at 1:53 PM

Since hearing the word orchestrator in ai context it was clear that ClanKernetes was coming.

verdvermtoday at 12:16 AM

I'm keeping an eye on another Google Cloud orchestrator

https://googlecloudplatform.github.io/scion/overview/

Scion wraps the harnesses (9x) we all use every day and is closer to OpenClaw on Kubernetes

motoboiyesterday at 11:48 PM

this is nice, basically virtual threads for kubernetes.

simianwordstoday at 8:50 AM

This is different from langchain etc because lanchain works at the app layer but this one works at the infra layer with tool calls etc?

rtcode_iotoday at 3:56 AM

Unnecessary complexity packaged as product!

joeyguerratoday at 2:13 AM

Am I being gaslighted into thinking over engineered systems are not?

mifydevtoday at 1:55 AM

Kubernetes is the last thing I wanted to see recreated for agents. It’s like Multics of cloud, now for agents. Complexity for the sake of it, powered by your favourite YAML slop bowl.

0xbadcafebeetoday at 12:51 AM

As usual, Google makes it "googley" by building an incompatible monolith with the kitchen sink included.

guluarteyesterday at 11:56 PM

I just have a tmux session acting as the orchestrator, and I tell it to report back and direct the other agents working in separate tmux sessions.

show 1 reply
dabeeeenstertoday at 8:06 AM

"2. Deploy the control plane

You need a Kubernetes cluster"

LOL. Bye!

aeon_aitoday at 12:33 AM

A DAG?! Holy innovation, Batman!

frank_clovertoday at 6:50 PM

[flagged]

nomad-linkd-idtoday at 3:08 PM

[flagged]

Sattyamjjaintoday at 6:55 PM

[dead]

aitoolcruxtoday at 11:55 AM

[flagged]

claud_iatoday at 10:02 AM

[flagged]

meherabhossaintoday at 8:17 AM

[dead]

sebastienbureltoday at 7:59 AM

[flagged]

mbarbertechtoday at 7:24 AM

[flagged]

dougametoday at 2:00 AM

[flagged]

kevinbaivtoday at 12:01 AM

[flagged]

robertclaustoday at 1:38 AM

[dead]

myshapeprotocoltoday at 7:27 AM

[dead]

ihswyesterday at 11:04 PM

[dead]

habajabtoday at 4:26 AM

[dead]