Claude Code 2.1.227

你明明訂了 Max 方案，剛開啟工作階段卻被催著替 Fable 開啟用量額度，感覺像進電影院時會員資料一時讀不到，售票員便誤以為你不是會員，要求你改辦一般票。問題出在登入 token（證明你已登入的數位令牌）過期時：功能旗標（feature flags，用來分批開啟功能的開關）檢查漏看了你的訂閱層級。現在即使一開始遇到過期 token，這項檢查也會帶上方案資訊，不會再錯誤提示 Max 用戶替 Fable 啟用 usage credits。

你把專案交給 GitHub 自動跑檢查，卻發現 Bash（在終端機執行指令的常用工具）每一條都失敗，像工地門口明明有施工名單，警衛卻把整班工人全攔下來。這次問題出現在 GitHub-hosted runner（GitHub 提供、替你執行自動化工作的雲端電腦）搭配 claude-code-action，而且設定了 allowed_non_write_users 時；這個設定是允許沒有寫入權限者執行的名單。現在這組設定下的 Bash 指令能正常執行，原本的允許名單不再反而讓工作完全停擺。

想把對話徹底倒回第一句以前、從空白重來時，最怕明明擦掉的內容又冒回畫面。先前若你把對話 rewind（倒回先前狀態）到第一則訊息之前，再輸入 /tui 開啟文字介面，舊對話可能被帶回來，像擦乾淨白板後按了開關，昨天的字又浮現。現在 /tui 會尊重你倒帶的位置：已倒到起點前的對話維持在那裡，不再被介面重新叫回。這是修正既有行為，不是新增一種刪除方式。

You may be on a Max plan yet get nudged to enable usage credits for Fable when a session opens. That was like a cinema clerk unable to read a member record and mistakenly asking a member to buy a regular ticket. If your login token had expired, feature flags were checked without your subscription tier. Those checks now include it, so Max users are no longer wrongly prompted to enable usage credits for Fable.

If GitHub is running checks for your project and every Bash command fails, the automation has become a worksite where the guard blocks every worker despite a valid list. This affected claude-code-action on GitHub-hosted runners when allowed_non_write_users was set—the list that permits users without write access. Bash commands now run normally with that setup, so the permission list no longer stops all work.

When you rewind a conversation to before its first message to start from a blank slate, erased words should stay erased. Previously, opening the text interface with /tui could bring that conversation back, like yesterday's writing reappearing after you wiped a whiteboard and flipped a switch. /tui now respects the rewind point: a conversation rewound before its start stays there instead of being revived by the interface. This fixes existing behavior; it does not add a new way to delete chats.