Antigravity 1.1.7

把一個外掛停用，理當它就該完全安靜下來。以前並不是——它的 hook（掛鉤，特定事件一發生就被自動觸發的小程式）照樣在背景執行，它帶進來的其他自訂設定也繼續生效。最難纏的情況是那個掛鉤本身已經壞了：它會一路卡住編輯檔案的工具，而你早就把外掛關了，根本不會回頭懷疑它，只能對著改不動的檔案發呆。現在停用就是真的停用，掛鉤和它夾帶的自訂設定一起下線。像員工離職卻沒繳回門禁卡，人不在了，卡還刷得開門，這次是連卡一起收回來。

公司拿 Salesforce 管客戶、拿 Atlassian 那套管專案，你想讓 AI 直接讀得到裡面的資料，卻總是卡在授權那一步。問題出在 MCP（Model Context Protocol，讓 AI 接上外部工具的協定）走的 OAuth 授權流程：這兩家的實作沒有完全照規範走，發行方資訊對不上，驗證就直接判失敗。現在比對發行方的條件放寬了，也把 refresh_token 這種續期方式一併帶上，授權到期時能自己換一張新的，不用你重登一次。像出國帶轉接頭，各國插座本來就不完全一樣，與其要求對方改插座，不如自己帶一個接得上的頭。

開一個全新的工作階段，什麼都還沒問，直接打 /btw 想先補一句題外話——以前這會當場失敗，丟回一句「找不到父對話」（parent conversation，指這句題外話原本該掛上去的那一則）。這種錯最讓人愣住：明明什麼都還沒做錯，第一個動作就撞牆，而且訊息講的是一個你根本沒聽過的東西。現在把它當開場第一個動作用，也能正常運作了。像剛拆封的筆記本，你想在第一頁就貼張便利貼，總不能因為前面沒有頁面而不讓你貼。

在 Windows 上複製一段中文、日文或韓文，貼出來變成一排問號和方框——這件事以前真的會發生。毛病出在送進剪貼簿的那一刻：ASCII（大致只涵蓋英文字母、數字與常見符號的老字碼表）以外的字元沒有被正確編碼，字在搬運途中就已經碎了，貼到哪裡都拼不回來。你想把一段錯誤訊息複製給同事看，對方收到的是一團看不懂的符號，只好請你截圖重來。這版把編碼修好了，複製什麼就貼出什麼。像影印機明明吃得下這張紙，印出來卻缺了半篇字，這次換掉的是機器本身。

Turn a plugin off and you would expect it to fall silent. It did not. Its hooks kept firing in the background, and the other customizations it brought along stayed in effect. The nastiest version of this was a hook that was already broken: it would jam the file-editing tools, and since you had disabled the plugin long ago, it never occurred to you to suspect it — you just sat there wondering why nothing would save. Disabling now really disables: the hooks and everything else the plugin contributed go quiet together. An employee leaves but keeps the door badge; the person is gone and the badge still opens the door. This time the badge comes back too.

Your company runs customers through Salesforce and projects through Atlassian, you want the AI to read from them directly, and you get stuck at authorization. The culprit is the OAuth flow behind MCP, the protocol that connects the AI to external tools: neither provider follows the spec to the letter, the issuer details fail to line up, and validation rejects the whole thing. Issuer validation is now relaxed, and the refresh_token grant is included, so an expiring authorization renews itself instead of sending you back to the login screen. It is the travel adapter approach: sockets genuinely differ between countries, and bringing a plug that fits beats demanding the country rewire.

You open a fresh session, ask nothing yet, and type /btw to drop in an aside first — and it used to fail on the spot with "parent conversation not found", the parent being the turn the aside was meant to hang off. Errors like this are the most disorienting kind: you have done nothing wrong, the very first thing you try hits a wall, and the message names something you have never heard of. Using it as the opening action now works. You have just unwrapped a notebook and want a sticky note on page one; the absence of earlier pages is no reason to refuse.

Copy a line of Chinese, Japanese or Korean on Windows and paste out a row of question marks and empty boxes — that really did happen. The damage occurred at the moment the text entered the clipboard: non-ASCII characters were not encoded correctly, so the characters were already broken in transit and no destination could reassemble them. You copy an error message to show a colleague, they receive a blob of symbols, and you end up sending a screenshot instead. The encoding is fixed: what you copy is what you paste. A photocopier that accepts the page but prints half the characters as noise does not need better paper; it needs a new machine.