問題修復
遠端任務不再因為「看起來太閒」而被誤殺
當你在無頭模式（headless session，沒有畫面的純背景執行模式）跑 Claude 時，如果剛啟動就在跑鉤子（hook，讓你在特定時間點自動觸發的腳本），以前它可能因為沒把進度回報出來，讓遠端系統以為它閒置太久（idle-reaped）而直接把它砍掉。現在進度會正常串流回報，確保系統知道它還在努力工作。就像一個在倉庫理貨的員工，以前因為沒出聲被主管當成在偷懶而直接開除，現在他會邊做事邊回報，就不會再被誤殺了。
繁體中文
English
BUGFIX
Remote tasks no longer get killed for "looking idle" during startup
When running Claude in a headless session (a purely background mode with no visible interface), if it was busy running startup hooks (scripts that automatically trigger at specific times) right after launching, the system used to sometimes fail to report its progress. This silence caused remote servers to assume it was idling (idle-reaped) and ruthlessly terminate it. Progress now streams correctly, proving it is still hard at work. It's like a warehouse worker who used to get fired for "slacking" because they were working quietly in the back; now they call out their progress as they go, avoiding wrongful termination.
原始 CHANGELOG
Original changelog遠端任務不再因為「看起來太閒」而被誤殺
Fixed hook events not streaming during SessionStart hooks in headless sessions, which could cause remote workers to be idle-reaped mid-hook