docs: focus user guides on features and workflows#9756
2 unresolved threads · Jump to file
0 / 23 viewed23 files changedLine totals unavailable
docs/user/keybindings.md · Earlier revision b55ac692 · right 20–21
Original diff
@@ -17,109 +16,63 @@ The file is a JSON array of rules. ] ``` -Invalid rules are ignored. An invalid file is ignored entirely, and the server logs a warning. +T3 Code creates the file with its defaults and adds new defaults on later startups. +New defaults do not replace commands you customized or take a shortcut already +used in the same context.
docs/user/keybindings.md · right 20–21
MmacroscopeappSep 4, 2026
🟡 Medium user/keybindings.md:20
A newly added default can override a user's existing shortcut after an upgrade when their when expressions overlap but are not textually identical. Conflict detection compares raw when strings, so a user rule for mod+x without when and a later default for mod+x with when: "!terminalFocus" both apply when the terminal is unfocused, and the default wins. Document this limitation instead of claiming such shortcuts are never taken.
suggestion
| 1 | New defaults do not replace commands you customized, but overlapping `when` expressions can still let a later default take a shortcut in some contexts. |
🚀 Reply "fix it for me" or copy this AI Prompt for your agent:
text
| 1 | In file @docs/user/keybindings.md around lines 20-21: |
| 2 | |
| 3 | A newly added default can override a user's existing shortcut after an upgrade when their `when` expressions overlap but are not textually identical. Conflict detection compares raw `when` strings, so a user rule for `mod+x` without `when` and a later default for `mod+x` with `when: "!terminalFocus"` both apply when the terminal is unfocused, and the default wins. Document this limitation instead of claiming such shortcuts are never taken. |
JJulius MarmingeSep 4, 2026
Fixed in 43a6ecf. The guide now explains that new defaults can overlap custom shortcuts and links to rule precedence. Verified the startup append order and last-matching-rule resolution.
docs/user/providers-antigravity.md · Earlier revision b55ac692 · right 65–67
Original diff
@@ -1,198 +1,135 @@ # Antigravity -T3 Code runs Google's official Antigravity ACP agent. By default it signs in with your personal -Google account and uses that account's Antigravity access, including access provided by a -Google AI subscription. It never falls back to a different sign-in method than the one you -select. - -The agent, files, conversation state, and Google credentials stay on the selected environment. -Your browser or phone controls that environment. Signing in to the Antigravity IDE or CLI does -not sign in this T3 Code provider. +T3 Code runs Google's official Antigravity ACP agent on your selected environment. +It has its own sign-in, separate from the Antigravity IDE or CLI. Google controls +which models and account access are available through this agent. ## Set up Antigravity -On web or desktop, open **Settings** > **Providers**, select the device that runs your project, -then select **Antigravity**. Provider setup is not available in the mobile app. - -1. Choose **Enable Antigravity**. Antigravity is off by default. -2. Choose **Install Antigravity**. T3 Code downloads the official runtime from Google to that - environment. Installation continues if you leave the page or reconnect. -3. Choose **Sign in with Google**. -4. Choose **Open sign-in page**. You can use **Copy sign-in link** to open it in another browser. -5. Complete Google sign-in. Use the account you use for Antigravity. -6. Wait for T3 Code to confirm sign-in and load the model choices. Select an Antigravity model - in the thread's model picker. +On web or desktop, open **Settings > Providers**, choose the environment that runs +your project, and enable Antigravity. Install its runtime there, then choose +**Sign in with Google** and complete the browser sign-in. Wait for T3 Code to confirm +account access and load models before starting a thread. Provider setup is not +available in the mobile app. -Setup requires a connection with permission to operate the environment. If setup is unavailable -on an older server, update that environment first. +Installation continues if you leave settings or reconnect. Setup requires +permission to operate the environment; update an older server if it does not offer +Antigravity setup. ### Sign in from a remote device -Google returns to a `127.0.0.1` address on the device running your browser. If that is the same -machine as the T3 Code environment, sign-in can finish directly. +Google returns to a `127.0.0.1` address. It can finish directly when your browser is +on the environment's machine. From another device, the final page will usually +fail to load because the sign-in listener is on the environment. -On a phone or another computer, the final page will usually fail to load. This is expected. -Copy the full address from the browser, including everything after `?`, and paste it into the -return URL field in the web or desktop client where you started setup. Choose **Continue**. Do not -change the address to your server's hostname. +Copy the full return address, including everything after `?`, into the return URL +field in the web or desktop client where you started setup, then choose +**Continue**. Keep the original address; do not replace it with the server's +hostname. Only that T3 Code sign-in session can finish the attempt. If it expires, +retry sign-in and use the new link. -Return to the same T3 Code client and environment where you started sign-in. Another client -can see that sign-in is in progress, but cannot complete that attempt. The setup screen shows -the expiry time. If it expires, choose **Retry Google sign-in** and use the new link. - -The return URL contains a temporary sign-in code. Paste it only into the setup field, not into -a thread or bug report. T3 Code waits for Google's agent to confirm sign-in. A successful -callback page alone does not prove account access. +The return URL contains a temporary sign-in code. Paste it only into the setup +field. A successful callback page alone does not confirm account access; wait for +T3 Code's confirmation. ### Other sign-in methods -**Sign-in method** in the Antigravity provider settings on web or desktop selects how the -agent authenticates. - -| Method | What you enter | How it signs in | -| -------------------------- | ---------------------------------------- | ------------------------------- | -| Google account | Nothing | Google sign-in page | -| Gemini Enterprise | GCP project and GCP location | Google sign-in page | -| Gemini API key | API key | Choose **Connect**. No browser. | -| Agent Platform (Vertex AI) | API key, or GCP project and GCP location | Choose **Connect**. No browser. | +Choose **Sign-in method** in the Antigravity provider settings: -Gemini Enterprise resolves your license for the project and location you enter. Agent Platform -with a project and location uses Application Default Credentials on the environment. API keys -are stored in plain text in T3 Code settings on that environment and are passed only to the -Antigravity agent process. Ambient `GEMINI_API_KEY` or `GOOGLE_*` variables on the environment -are ignored. +| Method | Credentials | +| -------------------------- | -------------------------------------------------------------------------------------------- | +| Google account | Personal Google sign-in in the browser | +| Gemini Enterprise | Browser sign-in, GCP project, and GCP location | +| Gemini API key | API key; choose Connect without a browser | +| Agent Platform / Vertex AI | API key, or GCP project and location with Application Default Credentials on the environment | -Changing the method stops the instance's sessions. Sign out or disconnect before you switch -accounts. +The Antigravity API key field is stored in plain text in settings on the +environment. The agent uses the method and credentials selected for this instance; +ambient `GEMINI_API_KEY` and Google credential variables do not override them. +Changing the method stops the instance's sessions. Sign out before replacing an +account. ## Runtime installation -Managed downloads are available for these environment hosts: - -| Host | Architecture | -| ------- | ------------- | -| macOS | Apple Silicon | -| Linux | x64 or ARM64 | -| Windows | x64 or ARM64 | - -Google does not publish a local Intel Mac runtime. Use an Intel Mac as a client connected to -a supported remote environment. - -The current Linux x64 runtime downloads about 682 MB and uses about 2.01 GB after extraction. -Allow at least 3 GB free for installation. An update keeps the previous runtime too. -T3 Code does not download it until you choose to install it. - -On web or desktop, **Update Antigravity** appears when T3 Code has a newer managed release. -Running sessions keep their current runtime. New sessions use the installed update. +Managed installation supports Apple Silicon macOS, Linux x64 or ARM64, and Windows +x64 or ARM64. Intel Macs can connect to a supported remote environment. Allow +several GB of free disk space, especially on Linux. ### Use a manual installation -Download the correct archive from the [official ACP Registry][registry] and extract both the -ACP executable and its `localharness_external` helper into the same directory. Keep both files -at the same version and make them executable on macOS or Linux. Windows uses `.exe` files. +Download the archive for your environment from the [official ACP Registry][registry]. +Extract the ACP executable and its `localharness_external` helper into the same +directory, at the same version. Make both executable on macOS or Linux; Windows +uses `.exe` files. -On web or desktop, set **Binary path** in the Antigravity provider settings to the ACP -executable on the selected environment. Do not point it at the helper or the Antigravity IDE. - -A nonempty **Binary path** takes priority. With the field empty, T3 Code uses its managed -runtime, then an installation on the environment's `PATH`. An invalid explicit path reports -an error instead of selecting another installation. T3 Code does not update or remove manual -installations. Clear **Binary path** to use managed installation controls. +Set **Binary path** to the ACP executable on the environment. This overrides +managed installation, so update the manual installation yourself. Clear the path +to return to managed installation.
docs/user/providers-antigravity.md · right 65–67
MmacroscopeappSep 4, 2026
🟡 Medium user/providers-antigravity.md:65
Clearing Binary path does not always return to the managed installation: when no managed release is installed, resolution falls through to a matching executable on PATH, so users can silently run an unmanaged runtime. Document this fallback so clearing the field does not imply the managed runtime will be used.
✅ Resolved in 43a6ecf8d92200dd65b3fd1bfcfa52980f865389
JJulius MarmingeSep 4, 2026
Fixed in 43a6ecf. Leaving Binary path blank now explicitly uses the managed runtime when installed, or a compatible executable on PATH otherwise. Verified against AntigravityInstallation.resolve and its existing path-resolution test.