Usage 0.14.0

想知道自己一天到底都在什麼時段用 AI，現在報表會直接畫給你看。分析報表新增了「Usage Habits（使用習慣）」段落，把一整天 24 小時的活動量畫成一條橫跨整個畫面的直方圖（histogram，一種用高低柱子表示數量多寡的長條圖），並標出你的尖峰時段，旁邊附一句白話摘要，像是「你最常在 HH:00 和 HH:00 這兩個時間點找 AI」。這份資料完全來自你本地 Claude Code 紀錄檔裡訊息的時間戳（timestamp，像 2026-07-14 14:30 這種標記訊息發送時刻的字串），而且只看使用者與 AI 助理訊息的時間點——**絕不碰對話內容**，你們聊了什麼完全不會被讀取。整個功能跑在你自己電腦上，不送任何資料到雲端、不呼叫任何 API。就像一個只看打卡時間、絕不偷瞄你電腦螢幕的書記，幫你整理出你最常在哪些時段上工。

現在當 Codex 的數字比較舊時，面板會直接告訴你「這是約 N 分鐘前的」，而不是讓你對著過時數字乾著急。Classic 面板的 Codex 卡片，當本地用量快照（snapshot，某個時間點拍下的資料定格照）超過 15 分鐘沒更新，就會顯示一個「about N minutes ago（約 N 分鐘前）」標籤，外加一個 ⓘ 資訊圖示的提示框（tooltip，滑鼠移上去才彈出的小說明）。為什麼會落後？因為跟 Claude Code 不同，Codex 沒有即時的狀態列掛鉤（status-line hook，一種讓程式把最新狀態即時塞進選單列的接掛點），它的用量數字只能靠它自己間歇寫進紀錄檔的工作階段（session）資料，自然會比你真實帳戶慢半拍。那個提示框也會說清楚：刻意保持離線、不上線查詢是設計選擇，為的就是絕不消耗你的 token（AI 計量的單位，回答越長花越多）。而這整個提示只用既有的 rate_limits.updated_at 欄位就能算出來——不用連網、不用 API。就像油耗表上如果數字是早上加油時記的，現在會貼一張「約 3 小時前」的便條提醒你別太相信，並附上說明：這台車刻意不連線回報，是為了不花你的通訊費。

Want to know which hours of the day you actually lean on AI? The report now charts it directly. The analysis report gained a new "Usage Habits" section that plots a full-width, 24-hour activity histogram (a chart of high and low bars showing how much activity falls in each slot), highlights your peak hour, and prints a plain-language summary beside it like "You most often work with AI around HH:00 and HH:00". The data comes entirely from the message timestamps (strings marking when each message was sent, like 2026-07-14 14:30) in your local Claude Code logs, looking only at the timing of user and assistant messages — **never the conversation content**; what you actually discussed is never read. The whole feature runs on your own machine, sending nothing to the cloud and calling no API. It's like a clerk who watches only the clock when you badge in and never glances at your screen, summing up which hours you work most.

When Codex's number goes stale, the panel now tells you straight up "this is about N minutes old" instead of leaving you staring at an outdated figure. On the classic panel's Codex card, once the local usage snapshot (a frozen data snapshot taken at one point in time) is older than 15 minutes, an "about N minutes ago" tag appears along with an ⓘ info tooltip (a small explanation that pops up when you hover). Why does it lag? Unlike Claude Code, Codex has no live status-line hook (a hookup point that lets a program push its latest state into the menu bar in real time), so its usage figures can only come from the session data it writes into its logs intermittently, naturally trailing your real account. The tooltip also explains that staying deliberately offline — not querying online — is a design choice so it never burns your token (the unit AI usage is metered in; longer answers cost more). And this entire hint is computed from the existing rate_limits.updated_at field — no network, no API. It's like a fuel gauge whose reading was taken at the morning fill-up now wearing a sticky note saying "about 3 hours ago" so you don't trust it blindly, with an attached note explaining: this car deliberately doesn't report in remotely, so it won't rack up your data charges.