Hello hello! This may not be the place to report this, as it is regarding the InteractionsAPI Antigravity Managed Agents, not necessarily the CLI or IDE. If this is not the right place then please disregard!
I have been building a CLI to use the @google/genai JS SDK and InteractionsAPI to provision Managed Agents, and have noticed a consistent issue. Despite containers being meant to be accessible for 7 days since the last interaction, around an hour after provisioning, they lose functionality. What I see from my end is that the Agent tries to invoke a basic tool call (list_files, execute_code, read_file) and gets back a 401 unauthorized error. To be clear, these are entirely internal tools, not custom functions provided by my CLI for the agent to call. It is entirely internal, too, not a call to an external source passed in via environment config. Once this error appears, that agent becomes unable to do anything and either resorts to just conversational text output, or sometimes gets confused and thinks it is being presented a puzzle or challenge to solve.
As I understand the intended behavior, passing a previousInteractionId and an environmentId should be enough to access a container with persisted context, but this error necessitates provisioning a new agent, and you lose the benefit of that persisted context.
With the new (as of July 7) ability to pass in a fresh network config to an existing environment, I had hoped that doing so would cause the container-side internal auth to refresh, but unfortunately that is not happening.
I’ve tried to be as descriptive as possible, though my visibility on the error/behavior is limited to what comes through the event stream. If this is the right place to report this, and more information is needed, I’m happy to help!