Antigravity 1.2.14

當你看到助理正朝錯誤方向執行長任務時，現在可以直接插話叫停。

你可以在 /config 選單找到 Queued Messages 選項。保持預設的 Queue 會把補充訊息暫存到當前輪次結束，切換成 Send Immediately 則能立即中斷助理。這項偏好也能直接寫入全域設定檔 settings.json，修正了以往寫入該設定卻被系統忽略的問題：

{"queuedMessages": "send-immediately"}

當你在輕量 Docker 環境裡想要連線操作時，過去常因底層缺少自動託管機制而直接碰壁卡關。

在沒有 systemd 使用者服務管理員（替個人帳號管理背景服務的程式）的 Linux 機器上執行 remote-control start 時，現在會直接將常駐程式以背景行程啟動，並警告該行程當機後不會自動重啟且開機時不會自動載入。你隨時能輸入 remote-control status 查詢其行程識別碼（PID），需要結束時輸入 remote-control stop 即可將其關閉。

當你接續聊了很久的繁重工作階段，或是中途遇上當機想接回紀錄時，整個流程順暢且安心許多。

重啟擁有數千步驟的對話時，命令列介面不再預先逐步掃描，載入速度明顯加快。歷程若曾因當機或寫入中斷而出現遺漏步驟，恢復時不會再隱藏最新內容，更不會讓新訊息意外覆寫舊紀錄。自動產生的對話標題現在也會將首則訊息附加的圖片與檔案納入考量，純傳截圖或檔案的請求也能擁有具體的標題。

早上一開工卻被擋在門外，畫面上只寫著因違反服務條款（Terms of Service）遭到停權，常讓人不知道該去哪裡詢問。以前遇到帳號受阻只能看見失敗提示，摸不清該找誰處理；現在登入失敗的錯誤訊息裡會直接附上申訴連結，讓你能立刻點擊網址提交說明。

當你為指令傳入結構描述時，若格式有誤或檔案遺失，系統在啟動階段就會立即攔截。

參數 --json-schema 不再將純文字、單獨型態名稱（如 string）或不存在的結構描述檔默默當成字串型態處理。現在只要輸入上述無效內容，或是根層級不是物件（"type": "object"）的結構描述，程式在啟動時就會直接輸出錯誤訊息並以結束代碼 1 中斷退出。

When you see your assistant heading in the wrong direction during a long task, you can now speak up and stop it directly.

You can find the Queued Messages option in the /config menu. Keeping the default Queue buffers follow-up messages until the current turn ends, while switching to Send Immediately interrupts the assistant right away. This preference can also be written directly to the global configuration file settings.json, fixing an issue where writing this setting previously got ignored by the system:

{"queuedMessages": "send-immediately"}

When you want to connect and operate inside a lightweight Docker environment, you previously hit a wall because the underlying system lacked an automated hosting mechanism.

When running remote-control start on Linux machines without a systemd user service manager (a program that manages background services for a user account), the daemon now starts directly as a background process, warning that the process will not restart on crash or launch on boot. You can enter remote-control status anytime to check its process ID (PID), and enter remote-control stop whenever you need to shut it down.

When you resume a heavy, long-running session or reconnect to your history after a crash, the entire workflow is noticeably smoother and safer.

When restarting conversations with thousands of steps, the command-line interface no longer pre-scans step-by-step, significantly speeding up load times. If history was missing steps due to crashes or interrupted writes, resuming will no longer hide the latest content, nor will new messages accidentally overwrite old records. Auto-generated conversation titles now also factor in images and files attached to the first message, giving concrete titles to requests that only include screenshots or files.

Starting your morning only to find yourself locked out, with a screen stating your account has been suspended for violating the Terms of Service, often leaves you wondering where to turn. Previously, encountering a blocked account only showed a generic failure message with no clear contact point; now, login failure error messages directly include an appeal link, letting you click the URL immediately to submit an explanation.

When you pass a schema to a command, the system now intercepts formatting errors or missing files right at startup.

The --json-schema parameter no longer silently treats plain text, bare type names (such as string), or non-existent schema files as string types. Supplying any of these invalid inputs, or a schema whose root level is not an object ("type": "object"), now causes the program to output an error message at startup and exit immediately with exit code 1.