Open History to see the last commit
1# Antigravity
2
3T3 Code runs Google's official Antigravity ACP agent on your selected environment.
4T3 manages its own CLI installation and sign-in, separate from your terminal or IDE. Google controls
5which models and account access are available through this agent.
6
7## Set up Antigravity
8
9On web or desktop, open **Settings > Providers**, choose the environment that runs
10your project, and enable Antigravity. Install its runtime there, then choose
11**Sign in** and complete the browser sign-in. Wait for T3 Code to confirm
12account access and load models before starting a thread. Once the runtime is installed,
13you can also sign in from **Settings > Providers** in the mobile app.
14
15Installation continues if you leave settings or reconnect. Setup requires
16permission to operate the environment; update an older server if it does not offer
17Antigravity setup.
18
19### Sign in from a remote device
20
21Google returns to a `127.0.0.1` address. It can finish directly when your browser is
22on the environment's machine. From another device, the final page will usually
23fail to load because the sign-in listener is on the environment.
24
25Copy the full return address, including everything after `?`, into the return URL
26field in the client where you started sign-in, then choose
27**Continue**. Keep the original address; do not replace it with the server's
28hostname. Only that T3 Code sign-in session can finish the attempt. If it expires,
29retry sign-in and use the new link.
30
31The return URL contains a temporary sign-in code. Paste it only into the setup
32field. A successful callback page alone does not confirm account access; wait for
33T3 Code's confirmation.
34
35### Other sign-in methods
36
37Choose **Sign-in method** in the Antigravity provider settings:
38
39| Method | Credentials |
40| -------------------------- | -------------------------------------------------------------------------------------------- |
41| Google account | Personal Google sign-in in the browser |
42| Gemini Enterprise | Browser sign-in, GCP project, and GCP location |
43| Gemini API key | API key; choose Connect without a browser |
44| Agent Platform / Vertex AI | API key, or GCP project and location with Application Default Credentials on the environment |
45
46The environment stores the Antigravity API key outside its settings file, and
47clients only see whether one is saved. The agent uses the method and credentials selected for this instance;
48ambient `GEMINI_API_KEY` and Google credential variables do not override them.
49Changing the method stops the instance's sessions. Sign out before replacing an
50account.
51
52## Runtime installation
53
54Managed installation supports Apple Silicon and Intel macOS, Linux x64 or ARM64
55with glibc or musl, and Windows x64 or ARM64. Allow at least 1.25 GiB of free disk
56space for downloading and staging an update.
57
58### Use a manual installation
59
60Install [Antigravity CLI](https://antigravity.google/docs/getting-started) on the environment.
61Set **Binary path** to its `agy` executable and update it yourself.
62Leave the field blank to use the managed runtime, or a compatible executable on
63`PATH` if no managed runtime is installed.
64
65## Update the managed runtime
66
67In web or desktop provider settings, choose **Update Antigravity** when an update
68is available. T3 checks Google's CLI release channel while provider update checks
69are enabled. Installing or reinstalling also checks that channel. Updates keep
70your profile and existing runtime available if the new release fails validation.
71
72Updating an older 1.4.5 installation migrates it to the native CLI. You may need to
73sign in again after migration. Threads already running finish with their original
74runtime; new sessions use the updated release. Custom binary paths keep using the
75executable you selected.
76
77## Models and threads
78
79The model list comes from your Antigravity account, including Claude and GPT models
80when your plan has them. Pick a thinking level beside the model list in the model picker; it
81shows only the levels the selected model supports. A resumed thread keeps its
82selected model. If access to that model ends, select another available model
83before continuing.
84
85Antigravity creates empty `.gemini/skills` and `.agents/skills` folders in the
86workspace when a session starts. Git does not track empty folders, so they never
87appear in commits.
88
89Use Antigravity's native `/plan` command for planning. Tool approvals follow [Permission modes](./permission-modes.md).
90Questions with fixed choices still need one of the offered answers, even in
91**Full access**.
92
93T3 Code keeps conversation history and file diffs, but Antigravity cannot rewind
94its conversation. Reverting a thread or editing and resubmitting an earlier turn
95is unavailable. Continue with a follow-up message or start a new thread.
96
97Manual context compaction is unavailable through Antigravity's ACP runtime, even
98though its CLI has `/compact`. Send `/clear` when you need a fresh context.
99
100### Skills and attachments
101
102Put project skills in `.agents/skills`. T3 Code also reads `.gemini/skills` and the
103legacy `.agent/skills` directory. Among these project locations, the first copy
104wins in this order: `.gemini/skills`, `.agents/skills`, `.agent/skills`. See
105[commands and skills](./composer.md#commands-and-skills) for invoking them.
106
107Skills for every project go in `~/.gemini/config/skills` or
108`~/.gemini/antigravity-cli/skills`. Antigravity does not read `~/.agents/skills`,
109so a skill there only appears when the project itself is your home directory.
110
111Antigravity receives images and audio directly, and reads PDFs and text files as
112documents. With the managed runtime on macOS and Linux, an MP4 video up to 20 MiB
113is sent as video to Gemini models. Other attachments, and videos for other models, are passed as a
114saved file path for the agent to inspect with its tools.
115
116### Subagents
117
118Antigravity groups subagent activity into batches. Open a batch and select
119**Subagent work** (**Work** on mobile) to read each child's role, prompt, and recent steps. This view
120is read only: you cannot message or control individual subagents, and an idle
121batch does not confirm that every child succeeded. If Antigravity did not record
122which children a batch started, the view says so. See
123[agent work](./thread-sidebar.md#inspect-agent-work) for where to inspect
124activity.
125
126## Accounts and removal
127
128Add an Antigravity provider instance for each Google account in
129**Settings > Providers** on web or desktop. Each has its own sign-in; downloaded
130runtimes are shared on the environment.
131
132| Action | Effect |
133| ------------------------- | ----------------------------------------------------------------- |
134| Disable | Stops the instance's sessions and keeps its Google sign-in. |
135| Sign out | Stops the instance's sessions and removes its saved Google login. |
136| Remove downloaded runtime | Removes the shared installation and keeps Google credentials. |
137
138All three keep thread history and workspace files. Sending `/logout` by itself in
139a thread signs out its instance, including stopping that instance's other sessions.
140Sign out, then sign in again to replace an account.
141
142Before removing a managed runtime, disable its instances and cancel any active
143installation. Clear any explicit binary path pointing into that runtime. Removal
144is refused while the runtime is in use.
145
146## Run a native goal
147
148When your Antigravity runtime offers `/goal`, send `/goal` followed by a verifiable
149objective. Antigravity keeps working until it completes the goal or you cancel it.
150If you still use the older 1.4.5 runtime, update Antigravity in provider settings,
151then refresh provider status.
152
153Use Stop to interrupt a running goal, then ask Antigravity to stop pursuing it
154before starting more work. Ordinary follow-ups wait until the running turn ends.
155T3 does not support Antigravity goal status, pause, resume, or clear commands.
156
157## Check access and troubleshoot
158
159Open **Usage > Limits** to see the remaining Gemini and shared Claude/GPT allowances
160for Google sign-ins. Each group has separate five-hour and weekly limits and reset
161times. Limits refresh with provider status and include usage outside T3 Code.
162
163A server restart keeps your Google sign-in. The provider shows the saved account
164until a session, a refresh, or a sign-out reports something new.
165
166To check access and reload models, use **Refresh provider status** in web or desktop
167provider settings, or **Refresh models** in mobile thread settings. If asked to
168sign in again, use provider settings on web or desktop, or **Settings > Providers** on mobile.
169
170If Google reports `SUBSCRIPTION_REQUIRED`, an account restriction, or a usage limit,
171follow the provider's message and any retry time. See [Google's account plans][plans]
172for eligibility.
173
174[plans]: https://antigravity.google/docs/plans