Release notes

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.

Original changelog

Original changelogCodex quota updates are now instantly responsive and resource-friendly
**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.