94 points blazarquasar 1 hour ago 33 comments
jmathai 1 hour ago | parent
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 expected Sheets + Gemini to be magical like Google Photos was. I hardly try anymore besides some basic math questions when I don't feel like inputting the formula myself.
The other thing I know is Google's propensity to sunset products. For many things, it's not a huge deal. And it may not be for this. But, why? When there are alternatives - both open and closed.
solidasparagus 1 hour ago | parent
Melonai 21 minutes ago | parent
TomGarden 1 hour ago | parent
Genuinely not knowledgeable here
AlexErrant 51 minutes ago | parent
https://grapheneos.social/@GrapheneOS/117282080803799576
> Google should not be gatekeeping security patches to the standard Android platform code from Android OEMs but that's what they've started doing.
blazarquasar 8 minutes ago | parent
jauntywundrkind 56 minutes ago | parent
I think Scion has so much more mature a disosition: you could write OpenCode plugins that enhance the runner, and use that locally, and use it in Scion. With Ax/Agent Substrate, you are opting in to a pretty huge stack that is just Agent Substrate, that is their runners, their harness, their substrate. I do think their actor model is pretty neat! It's neat having the agent have such primacy! But it feels so much less integrative, is such it's own thing. Scion, to me, is much more interesting an effort, that similarly helps scale out agentic workloads.
solarkraft 30 minutes ago | parent
The website makes me think the contrary: It is described as “low opinion” and explicitly mentions that the running tasks don’t even have to be AI agents. Can you explain in what ways you’re more locked in than the website suggests?
Scion at the same time talks much more about concrete agents, giving me the opposite initial impression.
pama 21 minutes ago | parent
> You need a Kubernetes cluster, ko (brew install ko), a container registry your cluster can pull from, and a reachable Agent Substrate Control API (in-cluster default: api.ate-system.svc.cluster.local:443).
> make deploy AX_IMAGE_REPO=<your-registry>
> This deploys Redis, then builds and deploys the control plane images with ko. Everything lands in the ax-system namespace.
Mond_ 50 minutes ago | parent
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.
foota 31 minutes ago | parent
Stagnant 29 minutes ago | parent
varun_ch 29 minutes ago | parent
mynegation 11 minutes ago | parent
skapadia 39 minutes ago | parent
lopatin 28 minutes ago | parent
motoboi 23 minutes ago | parent
mentalgear 19 minutes ago | parent
Would be about time we get benchmarks for these ... so these can also be gamified just like with the LLMs.
quadrature 5 minutes ago | parent
DanMcInerney 18 minutes ago | parent
handfuloflight 3 minutes ago | parent
guluarte 15 minutes ago | parent
kundi 13 minutes ago | parent
chrismarlow9 3 minutes ago | parent
Overall I agree though, this is a bit of an abuse of that concept.
mcoliver 2 minutes ago | parent
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, Cline, Aider, Qwen Code, Goose, Pi, OpenCode, something else? Can I modify the antigravity settings/program to point to a local model? Where should I spend my energy?