To make the review of your request easier, please use the following template to provide all the required details and also include any other information that may be relevant.
name: antigravity
description: Antigravity is Google’s agentic development platform. One can run multiple parallel agent sessions across multiple repositories. It is a new-era IDE.
reasoning: The harness needs to execute tools returned by the LLM model backing the agent. This is frequently Python, curl, git, etc. it could be just about any common command line tool that the model runs under the user’s supervision or delegation to proceed with the prompt. As the list of tools is potentially long and undefined, all the tools cannot be packed into the snap.
I understand that strict confinement is generally preferred over classic.
I’ve tried the existing interfaces to make the snap to work under strict confinement.
Note that snappy-debug can be used to identify possible required interfaces. See https://snapcraft.io/docs/debug-snaps for more information.
Whilst the technical reasons are clear to me, there’s an ongoing internal discussion as to what the policies should be around AI agents. I’ll be back once there is some clarity around it.
This should be allowed on the same grounds as Opencode.
Opencode is currently published under ubuntu-snaps, and given that the code for the Antigravity snap is in a Canonical owned repo, perhaps the first step should be transferring the snap to the ubuntu-snaps account, then granting classic.
@zyga One assumes you have access to that ubuntu-snaps namespace?
Yes, I didn’t say this aloud but it was my intent all along. The snap is basically ready and is maintained in the afforementioned repository, just needs to be published for the first time.
EDIT: Wrong snap, sorry, it’s late I confused this with my request for bun. I do have access to the ubuntu-snaps namespace.
I confused this with my request for bun. I do have access to the ubuntu-snaps namespace.