Actor/Worker Antigravity CLI example#199
Actor/Worker Antigravity CLI example#199Michael Levan (AdminTurnedDevOps) wants to merge 3 commits into
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
| @@ -0,0 +1,124 @@ | |||
| # Gemini CLI Multiplex Demo | |||
|
|
|||
| A demo of three Gemini-CLI-driven agents sharing two Agent Substrate pods. Substrate suspends idle agents and resumes them on demand, so the cluster runs *fewer pods than agents*. | |||
There was a problem hiding this comment.
Should this be antigravity since Gemini-cli is deprecated?
There was a problem hiding this comment.
This is a really good point. I'm going to switch this up.
There was a problem hiding this comment.
I'm not affilated with google so I don't care on antigravity as the option.
I've been trying to change to use opencode / pi as that they are easily interchangeable for different models.
There was a problem hiding this comment.
Yeah, makes sense and nah, I hear you. Gemini CLI is going to be deprecated I believe end of June, so it makes sense to not have a demo on this.
There was a problem hiding this comment.
Just pushed the change to be antigravity instead of gemini.
|
See Also: https://github.com/google/ax google/ax#80 |
Dmitry Berkovich (dberkov)
left a comment
There was a problem hiding this comment.
Michael Levan (@AdminTurnedDevOps)
- Could you please sync your fork to mainline. Your gvisor-ateom has an old version. I was able to make your code running, however at some point worker was throwing an error:
{"time":"2026-06-13T19:19:42.117690053Z","level":"ERROR","msg":"Error while executing","err":"ateom socket path \"/run/ateom-gvisor/ateoms/antigravity-cli-multiplex-demo:antigravity-workerpool-deployment-58dcb5db58-qsx25/ateom.sock\" is 117 bytes, exceeds Linux unix-socket limit of 107: shorten the namespace or pod name (30 + 50 = 80 chars used for namespace + name)"}
I shorten the namespace and was able actors to be registered.
- What UI supposed to do? I pressed "Give task" button and saw a new TASK added, the state state changed from QUEUED -> RUNNING -> COMPLETED, however I did not see any workers being RUNNING and/or new ACTORS are created. The
kubectl get actorsdoes not show new actors being created.
Signed-off-by: adminturneddevops <mlevan1992@gmail.com>
9b9b19b to
f5139dc
Compare
Hey Dmitry, hope all is well! I synced with In terms of the UI, I went off of what was in the Claude example. My understanding is the UI is there as an example because there's no interaction point/"client" for Substrate, so the only way to resume Actors is to |
Could you please clarify what is a purpose of this demo? |
Goal was to have a demo like the Claude demo thats already in the repo, but for antigravity (as it's a Google OSS project, figured having a way to showcase it with a Google product would be cool). I'm happy to just put this in one of my demo repos those outside of this if you prefer. |
|
Michael Levan (@AdminTurnedDevOps) the problem the current demo does not work or missing instructions. Therefore it cannot be submitted as is. In addition to it, anti-gravity requires GEMINI_API_KEY to work and it is missing in your demo too. |
Created an example for Gemini CLI (mimics the Claude Code example).
Tested to ensure pods, workerpool, and actortemplates are up and operational.
logs from the workerpool deployment:
^ Saw this error, so I added in
/run.shin the template (per upstream issue #189 — "Atelet OCI bundle gaps).Worked as expected after:
Resumed the Actor and ran a quick test: