Claude Code 2.1.225

沒有畫面的 headless（無頭模式，沒有終端機視窗的執行方式）工作跑到一半，碰上一個暫時的 401 錯誤，以前可能被換成短命登入 token（授權令牌，用來證明登入身分的通行碼），得重啟才救得回來。macOS 的 MCP OAuth 伺服器也會在鑰匙圈讀取逾時後，突然連發 401，像從沒登入過。現在兩種狀況都修正了。這像交通卡讀卡器一時失靈，卻把你的月票剪成單次票；它現在不會亂換卡。

自動模式（auto mode，Claude 自己執行操作、逐步少問一次的模式）要請權限卻被安全篩選器拒絕時，操作仍會被擋下；這次拒絕不計入連續受阻次數，模型會收到往下做的提示，改往其他可繼續做的步驟前進，不再重試。像自助結帳機刷不過某張折價券，店員仍不讓它通過，但也不會讓機器一直重刷同一張；它會改成繼續處理購物籃裡的其他東西。

你在沒有畫面的 headless（無頭模式，沒有終端機視窗的執行方式）環境，或 Claude Code 剛啟動時傳跨工作階段訊息，過去訊息可能停在佇列裡，既不提醒也不會過期。現在這個問題修好了，不必再像盯著一直沒叫號的號碼牌那樣等著。跨工作階段訊息是不同 Claude 工作階段之間的傳話；它該送達、該告知時就會有明確結果，而非悄悄停住。

用 Remote Control（遠端控制，從另一台裝置查看或接手 Claude 工作）接續超長對話時，先前壓縮過的聊天記錄可能讓恢復失敗；網頁工作階段還會被誤判卡住，每次重連又重送更多舊事件。現在這兩處都修正。它像接續播放清單：以前播放器既找不到停下的位置，又把已播曲目一首首重放；現在能從原處接回，也不會讓舊內容越疊越厚。

agents 清單裡把滑鼠移到另一個專案的工作階段上，下一個 agent 以前可能改在那個專案的資料夾啟動，現在不會了。另一邊，claude self-hosted-runner 的 --base-dir 若無法建立或寫入，過去會先註冊、每個工作階段才失敗；現在啟動時就明白報錯並退出。像派車中心不再因瞄到隔壁訂單就把司機派錯地址，車庫門打不開也會在出車前說清楚，不會每趟才拋錨。

想請另一台機器上的 Remote Control 工作階段幫忙，現在 SendMessage 可依名稱直接開啟對話，不必等對方先傳話。ListAgents 會把它顯示成 name [ref]，方便辨認遠端對象。你確認過的遠端收件人，也不會因本機剛好有同名工作階段、而且清單查不到遠端時，被偷偷換成那一個。像依取件編號交付物品：先用名稱和編號認出指定對象；即使遇到同名者，已確認的對象也不會被換掉。

A headless job can run without a terminal window. During one, a temporary 401 error used to replace a long-lived CLAUDE_CODE_OAUTH_TOKEN with a short-lived login token, breaking the job until restart. On macOS, MCP OAuth servers could also emit a burst of 401s after a Keychain read timed out. Both cases are fixed. It was like a transit-card reader briefly failing and then cutting your monthly pass into a one-trip ticket; it no longer swaps the card.

When auto mode asks for permission and a safety filter refuses that check, the action still stays blocked. The refusal no longer counts toward the consecutive-block limit, and the model is told to move on rather than retry. Think of a self-checkout that cannot accept one coupon: staff still reject it, but do not make the machine scan the same coupon forever; it continues with the rest of the basket.

Send a message between Claude sessions from a headless environment, or during startup, and it could previously sit in a queue with neither notice nor expiry. That is fixed. A cross-session message is a handoff between separate Claude sessions; it should now produce an outcome rather than resemble a letter wedged silently inside a mailbox. You no longer need to wonder whether it is waiting forever.

With Remote Control, you can inspect or take over Claude work from another device. Resuming a huge conversation after its history was compacted could fail, while web sessions could be falsely called stuck and resend an ever-growing backlog on each reconnect. Both are fixed. It was like rejoining an online meeting where the host lost the first half of the notes and replayed every old slide; now the meeting resumes where it stopped without piling up history.

Hovering over a session from another project in the agents list could previously change the folder where the next agent started. It no longer does. Separately, if claude self-hosted-runner cannot create or write its --base-dir, it now exits with a clear startup error instead of registering and failing every session. It is like dispatch no longer sending a driver to a neighbor's address after glancing at their order, and reporting a locked garage before every trip breaks down.

Want help from a Remote Control session on another machine? SendMessage can now start a conversation with it by name; you no longer have to wait for it to write first. ListAgents shows it as name [ref]. A Remote Control recipient you already confirmed also cannot be silently replaced by a same-named local session if its remote list cannot be checked. It is registered mail: find the addressed recipient first, and do not hand the confirmed letter to a namesake.