發布日期：2026-10-07
檢查 AI 修改的多個檔案時，/diff 畫面的跨檔案切換變得非常流暢。
按左右箭頭 ← 與 → 切換檔案時，畫面會跳到該檔案的第一個修改區塊，並顯示區塊標頭與修改處前面的文字。每個檔案會記住游標與捲動位置，切換檔案或回到檔案清單後都不會跑位。按 n 或 N 能繼續跳到下一個或上一個檔案的變更，不再停在當前檔案的最後一處修改。頂端標頭新增靠右的 change A/B · file X/Y，標示游標所在的增刪區塊與檔案順序。只有一個檔案變更時省略檔案計數，終端機太窄時隱藏位置標示。底部按鍵提示移除通用的捲動與翻頁說明，視窗太窄時會換行，不再被切斷。
想要在長對話中退回先前的討論進度時，歷史訊息的呈現更加明確。以前為了節省空間而清掉的舊訊息，在 /rewind 清單中會顯示為 (empty message)，一旦選取就會發生錯誤。現在這些已清理的訊息會保留原本的文字內容，以淡化樣式標註 cleared to save space, can't rewind here，並且無法再被選取，避免你不小心點到無法退回的段落。
在 Windows 系統上使用 /plugin 管理外掛時，安裝與移除流程現在更穩定。以前如果外掛的 MCP（讓 AI 連接外部工具的協定）伺服器仍在執行，檔案操作便會失敗。現在指令列介面會在替換或刪除資料夾前先停止相關伺服器，完成後再重新啟動。要是有另一個 agy 工作階段、Antigravity Hub 或 remote-control 背景守護程序仍佔用該外掛，也會提示你關閉該程式後重試。包含 UTF-8 位元組順序標記（BOM，部分編輯器存檔時附加在檔頭、用來辨識文字編碼的特殊標記）的外掛資訊清單、mcp_config.json 與 hooks.json 檔案現在都能正常讀取。從市集安裝外掛時，也不會再意外覆寫來自其他來源的既有外掛資料夾。
為自訂 Agent 撰寫 Markdown 設定檔時，引入附屬資源的方式變得更直覺。以前無論作為主要 Agent 或子代理（由主要 Agent 派工的輔助代理）執行，檔案內以相對路徑指定的 skills:、plugins:、rules:、agents: 與 hooks: 都會被忽略。現在這些設定會以該 Agent 檔案所在的目錄為基準進行解析，例如在設定中寫入 agents: [child.md] 就能順利呼叫 child，方便將相關技能與子代理打包在一起。
派遣子代理在背景處理任務時，執行狀態的呈現更加精確。以前子代理若因額度耗盡或模型算力不足而中斷，在 /agents 與執行中的代理清單中仍會被誤標為 Done。現在遇到問題時會明確顯示 Error: 以及具體的出錯原因，且只要該子代理後續重新取得進展，錯誤標記便會自動清除，方便你隨時掌握背景作業的真實進度。
透過終端機追蹤各項背景工作時，任務清單現在能掌握全部作業。以前 /tasks、作用中任務清單以及終端機狀態列（顯示在終端機底部的狀態資訊）的任務計數，都只會記錄背景 Shell 指令。現在 AI 排程的單次計時器、循環定時工作，以及其他在背景運行的工具都會一併列出。這些任務會明確標示為 completed 或 failed，不再附帶虛構的結束代碼。
如果你想在 AI 回覆中途插話補充指令，訊息能更即時地送達。以前如果在 /config 中將 Queued Messages 設定為 Send Immediately 立即傳送，只要 AI 在該回合中建立或更新了任務清單或計畫等產物，你的輸入就會被悄悄排隊延後，直到整次回合結束前 AI 都不會看到你剛才輸入的內容。現在訊息會立刻傳遞給 AI，確保你的即時指示能馬上發揮作用。
將終端機切換到背景執行時，AI 的提問能第一時間提醒你。以前在 /config 開啟了 Notifications 通知功能，AI 停下來向你詢問問題時，終端機卻不會跳出提示，導致作業在背景乾等。現在指令列介面會像跳出工具授權提示那樣，針對待回覆的問題發出提醒通知，讓你隨時接手確認。
調整外部工具連線時，重新啟動伺服器的流程變得更可靠。以前透過 /mcp 重新啟動 MCP（讓 AI 連接外部工具的協定）伺服器時，若舊的伺服器行程關閉耗時過久，可能會出現 Failed to stop existing instances for reload: ... signal: killed 等錯誤並停留在停止狀態。現在這個問題已經修好，無論舊行程關閉耗時多久，伺服器都會順利重新啟動。
遇到帳號狀態異常或條款限制時，錯誤訊息能提供更具體的解決途徑。以前帳號若需要驗證身分或申訴服務條款（Terms of Service）封鎖，登入錯誤有時只會顯示 Verify your account to continue. 卻沒有附上任何網址，甚至建議你登出再重新登入。現在畫面一律會提供驗證或申訴的連結，且在重新登入沒有幫助的情況下不再給出無效的登出建議。
使用自訂金鑰連線時，網路短暫斷線不再導致工作階段整次回合失敗。以前在透過 GEMINI_API_KEY 執行的工作階段中，若內部與 Gemini API 的連線不小心斷開，整次回合會直接失敗並顯示為如同被你手動取消一樣。現在指令列介面遇到內部斷線時會改為自動重試請求，不必再手動重新輸入。
When inspecting multiple files modified by AI, switching between files in the /diff view is now much smoother.
Pressing the left and right arrows ← and → to switch files jumps to the first modified chunk of that file and displays the chunk header along with the text preceding the edit. Each file remembers its cursor and scroll position so nothing shifts when switching files or returning to the file list. Pressing n or N continues jumping to the next or previous file's changes instead of stopping at the last modification in the current file. The top header adds a right-aligned change A/B · file X/Y indicator that marks the cursor's addition/deletion chunk and file order. When only one file changes, the file count is omitted, and the position indicator is hidden if the terminal is too narrow. Bottom key hints remove generic scrolling and paging descriptions, wrapping onto a new line when the window is too narrow so they are no longer cut off.
When rewinding to an earlier point in a long conversation, historical messages are now displayed much more clearly. Previously, older messages cleared to save space appeared as (empty message) in the /rewind list, throwing an error if selected. These cleared messages now retain their original text content, are labeled with a dimmed cleared to save space, can't rewind here style, and can no longer be selected, preventing you from accidentally choosing an unrewindable section.
When managing plugins with /plugin on Windows, installation and removal are now more reliable. Previously, file operations would fail if the plugin's MCP (a protocol that lets AI connect to external tools) server was still running. The CLI now stops the relevant servers before replacing or deleting folders, restarting them once complete. If another agy session, Antigravity Hub, or remote-control background daemon still locks the plugin, it will prompt you to close that process and retry. Plugin manifests, mcp_config.json, and hooks.json files containing a UTF-8 byte order mark (BOM) can now be read properly. Some editors add this marker at the beginning of a file to identify its text encoding. Installing plugins from the marketplace will also no longer accidentally overwrite existing plugin folders from other sources.
When writing Markdown config files for custom agents, referencing companion resources is now much more intuitive. Previously, relative paths specified in skills:, plugins:, rules:, agents:, and hooks: were ignored whether running as the main agent or as a subagent (a supporting agent assigned tasks by the main agent). These settings are now resolved relative to the directory containing that agent file. For example, writing agents: [child.md] in the configuration successfully invokes child, making it easy to package related skills and subagents together.
When delegating background tasks to subagents, execution statuses are displayed much more accurately. Previously, if a subagent stopped due to exhausted quota or insufficient model capacity, it was still incorrectly marked as Done in /agents and the active agents list. It now clearly shows Error: alongside the specific cause of failure whenever an issue occurs. As soon as the subagent makes further progress later, the error badge is automatically cleared, allowing you to track the actual status of background operations at all times.
When tracking background jobs through the terminal, the task list now captures all operations. Previously, /tasks, the active task list, and the terminal status line (status information displayed at the bottom of the terminal) task counter only tracked background shell commands. Single-shot timers scheduled by AI, recurring scheduled jobs, and other tools running in the background are now listed as well. These tasks are clearly labeled as completed or failed without attaching fabricated exit codes.
If you want to interject instructions while the AI is replying, messages are now delivered much more promptly. Previously, when Queued Messages was set to Send Immediately in /config, your input was silently queued and delayed whenever the AI created or updated artifacts like task lists or plans during that turn, preventing the AI from seeing what you typed until the entire turn finished. Messages are now delivered to the AI immediately, ensuring your real-time instructions take effect right away.
When running the terminal in the background, questions from the AI can now alert you immediately. Previously, even with Notifications enabled in /config, no prompt popped up in the terminal when the AI stopped to ask you a question, leaving the job waiting in the background. The CLI now emits reminder notifications for pending questions just like it does for tool approval prompts, allowing you to take over and confirm at any time.
When adjusting external tool connections, restarting servers is now more dependable. Previously, restarting an MCP (a protocol that lets AI connect to external tools) server via /mcp could trigger errors like Failed to stop existing instances for reload: ... signal: killed and remain stopped if the old server process took too long to shut down. This issue has been fixed so that the server restarts smoothly regardless of how long the old process takes to terminate.
When encountering abnormal account statuses or terms restrictions, error messages provide clearer resolution paths. Previously, if an account needed identity verification or needed to appeal a Terms of Service ban, login errors sometimes only showed Verify your account to continue. without any URL, even suggesting that you log out and log back in. The screen now consistently provides verification or appeal links and no longer suggests an unhelpful logout when re-logging in would not resolve the issue.
When connecting with a custom key, brief network disconnects no longer cause an entire session turn to fail. Previously, in sessions running via GEMINI_API_KEY, if the internal connection to the Gemini API was unexpectedly interrupted, the entire turn would fail immediately and appear as though you had manually cancelled it. Now, the command-line interface automatically retries requests upon internal disconnects, so you no longer need to re-enter them manually.
Improved navigation in the `/diff` file view: `←`/`→` now open the next or previous file at its first change with the hunk header and leading context in view, each file remembers its cursor and scroll position when you switch files or go back to the file list, `n`/`N` continue into the next or previous file's changes instead of stopping at the last change in the current file, and the key-hint footer drops the generic scroll and page hints and wraps onto extra lines instead of being cut off on narrow terminals.
Improved the `/diff` file view header to show where you are: it now ends with a right-aligned `change A/B · file X/Y` position, counting the block of added or removed lines under the cursor and the file's place in the file list (`file X/Y` is left out when only one file changed, and the position is hidden on narrow terminals).Fixed `/rewind` in very long conversations listing older messages as `(empty message)` and failing with an error when you picked one: messages that were cleared to save space now show their original text, dimmed and labeled `cleared to save space, can't rewind here`, and can no longer be selected.Fixed installing, reinstalling, and uninstalling plugins with `/plugin` on Windows failing while one of the plugin's MCP servers was running: the CLI now stops the plugin's MCP servers before replacing or deleting its folder and restarts them afterwards, and if another Antigravity process such as another `agy` session, the Antigravity Hub, or the `remote-control` daemon still holds the plugin open, it tells you to close it and retry. Plugin manifests, `mcp_config.json`, and `hooks.json` files saved with a UTF-8 byte-order mark now load, and installing from a marketplace no longer overwrites an existing plugin folder that came from a different source.Fixed markdown custom agents ignoring `skills:`, `plugins:`, `rules:`, `agents:`, and `hooks:` entries written as paths relative to the agent's own file when the agent ran as a subagent or as the main agent; such entries now resolve against the agent's directory, so an agent that lists `agents: [child.md]` can invoke `child`.Fixed subagents that stopped on an error, such as running out of quota or model capacity, being shown as `Done` in `/agents` and the list of running agents; they now show `Error:` with the reason, and the error clears once the subagent makes further progress.Fixed `/tasks`, the active task list, and the status line's task count showing only background shell commands; timers and recurring jobs the agent schedules, and other tools running in the background, now appear there too and are shown as `completed` or `failed` without a made-up exit code.Fixed messages sent with `Queued Messages` set to `Send Immediately` in `/config` being silently queued until the end of the turn whenever the agent had already written or updated an artifact, such as a task list or plan, during that turn; they now reach the agent right away.Fixed terminal notifications not firing when the agent stops to ask you a question; with `Notifications` turned on in `/config`, the CLI now alerts you for pending questions just as it does for tool permission prompts.Fixed restarting an MCP server from `/mcp` sometimes leaving it stopped, with an error such as `Failed to stop existing instances for reload: ... signal: killed`, when the old server process took too long to exit; the server now always starts again.Fixed the sign-in error for accounts that need to verify their identity or appeal a Terms of Service block sometimes showing only `Verify your account to continue.` with no link; the verification or appeal link now always appears, and the CLI no longer suggests logging out and back in when that would not help.Fixed `GEMINI_API_KEY` sessions failing a turn as if you had cancelled it when the connection to the Gemini API was dropped internally; the CLI now retries the request instead.