繁體中文

問題修復

Codex 額度更新不再慢半拍,背後也不再偷吃系統資源

你的 Codex 額度顯示現在更即時,電腦資源也不會再被偷偷吃掉了。當系統在背景重新抓取額度時,以前會等所有笨重的歷史紀錄都掃描完,才把最新的 Codex 額度貼上畫面,導致這中間畫面會短暫閃出過期的舊數字;現在它學會一拿到新額度就立刻送上畫面,不再慢半拍。另外,以前在讀取 Codex 的本機紀錄檔(SQLite 資料庫)時,只結束了動作卻沒把檔案關好,時間久了會累積一堆沒關的檔案通道、偷偷吃掉系統資源;現在每次讀完都會確實把門關上。就像是餐廳服務生以前要等整張清單的菜都做完才一次端上桌,現在有熱騰騰的菜就先上;而且收盤子時也不會再把推車丟在走道上擋路了。

English

BUGFIX

Codex quota updates are now instantly responsive and resource-friendly

Your Codex quota display is now instantly responsive, and your computer's resources will no longer be quietly drained in the background. Previously, during a background refresh, the system would wait until the heavy project history scan completely finished before dispatching the fresh Codex quota to the UI, causing the screen to briefly flash a stale number. Now, the new quota is sent to the screen the exact second it's fetched. Additionally, when reading Codex's local history files (SQLite databases), the system used to finish the transaction but forget to explicitly close the file connection, slowly leaking file descriptors over time and quietly eating up system resources; it now strictly closes the door after every read. It's like a waiter who used to wait until an entire massive order was cooked before bringing out any food; now they bring out hot dishes immediately. Plus, they no longer leave empty carts cluttering the aisles after bussing tables.

原始 CHANGELOG

Original changelogCodex 額度更新不再慢半拍,背後也不再偷吃系統資源
**Fixed a file-descriptor leak from Codex SQLite connections not being closed after reads (#30)**: reading Codex's `logs_2.sqlite` / `state_5.sqlite` only ended the transaction without actually closing the connection, accumulating open file descriptors over long runs. Connections are now properly closed after every read.
**Codex quota refresh is now applied before the history scan (#31)**: during background refresh, the Codex quota result is now applied to the main view synchronously before the project history scan runs, avoiding a brief display of stale quota.