發布日期：2026-10-07
當你跟 AI 進行長篇對話時，往往需要留意用量是否快要超出容量上限。
上下文視窗現在會依照總容量來判斷顏色。用量達到 50% 或 200K token（AI 處理與計費的文字單位）時會變黃，達到 80% 或 400K token 時則變紅，並以先達到的一項為準。上下文容量為 1M 時，用量大約達到 20% 就會變黃；至於上下文容量為 200K 時，變色門檻則維持不變。Claude Code 側邊面板的警示標準也從原本的 70% 與 85% 改為這套新規則，讓側邊面板與狀態列的顏色完全保持一致。
如果你習慣讓 AI 給出簡潔俐落的答案，開啟精簡模式時會發現回覆變得乾淨明快。
精簡模式現在強制一句話只講一件事，一律採用主動語態，並針對同一概念使用一致的詞彙。回覆長度也依照語言設下嚴格上限，中文限制 30 字、日文與韓文限制 40 字，英文則約為 20 個單字。負責這項功能的精簡模式 hook（掛鉤，特定事件發生時被觸發的小程式）版本已升級至 1.7，已安裝的副本會在下次開啟應用程式時自動更新。
把大量程式碼和截圖丟進對話後，一旦看到用量亮起警告，往往很難一眼看出到底是哪類內容在吃容量。
當上下文（AI 在對話中能參考的內容）用量的數字變黃或變紅時，顯示在終端機最底下的狀態列會主動列出圖片數量，以及讀取檔案與指令輸出的估計佔比，例如 圖片 3 張 · 讀檔與指令輸出 22%。若該比例偏高，會建議你開啟新的對話工作階段。當狀態列空間不足時，這段組成資訊會最先被省略。狀態列 hook（掛鉤，特定事件發生時被觸發的小程式）已升級至 1.14，已安裝的副本會在下次開啟應用程式時更新。
每次應用程式自動升級之後，你往往需要確認剛剛到底改了哪些功能。
現在更新後第一次開啟應用程式，畫面會主動跳出這一版的更新內容，而且只會顯示一次。全新安裝的使用者不會看到這項提示；若啟動時沒有網路連線，會在下次開啟時再次嘗試顯示。這項功能同時適用於 macOS 與 Windows 系統。更新提示中每項變更只會列出一行，中文使用者會看到繁體中文說明，其他語言的使用者則會看到英文。由於提示視窗是由你目前安裝的版本所繪製，多語言更新說明會從這版之後的下一版更新提示開始正式生效。
如果你在 macOS 上下載應用程式後習慣手動驗證安全性，以前可能會因為簽章失效而無法通過檢查。
現在打包流程在清除位元組碼快取（cache，把編譯結果暫存起來直接用的檔案）後會重新進行數位簽章。下載後的應用程式副本都能順利通過 codesign --verify 驗證，讓程式碼簽章恢復有效。
During long conversations with AI, you often need to keep an eye on whether usage is nearing capacity limits.
The context window now determines its color based on total capacity. Usage turns yellow at 50% or 200K tokens (units of text used for AI processing and billing), and turns red at 80% or 400K tokens, whichever threshold is reached first. With a 1M context window, usage turns yellow at roughly 20%; for a 200K context window, the color thresholds remain unchanged. Claude Code sidebar panel alerts have also switched to these new rules from the previous 70% and 85% marks, keeping colors between the sidebar panel and status line fully consistent.
If you prefer crisp answers from AI, turning on concise mode makes responses noticeably clear and punchy.
Concise mode now enforces one idea per sentence, strictly adopts the active voice, and applies consistent terms for the same concept. Response length is also capped by language: 30 characters for Chinese, 40 characters for Japanese and Korean, and roughly 20 words for English. The concise mode hook (a small program triggered by a specific event) handling this feature has been upgraded to version 1.7, and installed copies will automatically update on the next application launch.
After pasting extensive code and screenshots into a conversation, seeing a usage warning often leaves you wondering which content type is consuming capacity.
The status line appears at the very bottom of the terminal. When context (the content AI can refer to in a conversation) usage numbers turn yellow or red, the status line actively displays image counts alongside estimated proportions for read files and command output, such as Images 3 · Files & commands 22%. If this percentage is high, it recommends starting a new conversation session. When status line space runs out, this breakdown information is omitted first. The status line hook (a small program triggered by a specific event) has been upgraded to 1.14, and installed copies will update on the next application launch.
Whenever the application updates automatically, you often want to verify which features changed.
When you launch the application for the first time after an update, a release notes prompt appears on screen and shows only once. Fresh installations will not display this prompt, and if there is no internet connection at startup, it will try again on the next launch. This feature is supported across macOS and Windows. Each change in the update prompt takes only one line; Chinese users see Traditional Chinese descriptions, while other users see English. Because the prompt window is rendered by your currently installed version, multilingual release notes will officially take effect starting with the update prompt in the subsequent release.
If you manually verify application security after downloading on macOS, invalid signatures may have previously caused checks to fail.
The packaging process now performs digital signing again after clearing bytecode caches. Downloaded application copies can now pass codesign --verify verification without issue, restoring valid code signatures.
**Context color now accounts for window size.** The figure turns yellow at 50% or 200K tokens and red at 80% or 400K tokens, whichever comes first. On a 1M window, yellow now appears at about 20%. 200K windows are unchanged.
**Side pane colors match the status line.** The Claude Code side pane moves from 70% / 85% to the same rule.**Terse mode uses shorter sentences.** Replies keep one idea per sentence, use active voice and consistent terms, and follow a length limit per language: about 20 words in English, 30 characters in Chinese, 40 in Japanese and Korean. The terse hook is now 1.7; installed copies update on the next app launch.**Context breakdown in the status line.** When the context figure turns yellow or red, the status line shows the image count and the estimated share of file reads and command output, for example `Images 3 · Files & commands 22%`. A high share suggests starting a new conversation. This segment is dropped first when space runs out. The status line hook is now 1.14; installed copies update on the next app launch.**Release notes after an update.** The first launch after an update shows what changed in that version, once. Fresh installs skip it. If the app is offline, it tries again on the next launch. macOS and Windows.
**Release notes in your language.** Update alerts list one line per change. Chinese users see Traditional Chinese; other languages see English. This applies to the update alert from the version after this one, because the alert is drawn by the version you already have.**The app's code signature is valid again.** The build re-signs the app after it removes bytecode caches, so `codesign --verify` passes on downloaded copies.