v1.6.0

New

• Request dumps are capped at 512 MiB by default (#230). With request dumps on, the dump folder used to grow without limit. Once the dump files in it pass 512 MiB, the oldest dumps are now deleted first, on OpenCode 1 and OpenCode 2. Other files in the folder are left alone. Change the cap with dumpMaxBytes in the config file or OPENCODE_OPENAI_AUTH_DUMP_MAX_BYTES, in bytes, where 0 turns the cap off. Cleanup runs in the background after a dump is written, at most once every five minutes, and the newest dumps are kept. So the folder can stay over the cap until a later dump triggers the next cleanup. /openai → Diagnostics shows the folder's current size and the cap while dumps are on. See Configuration for the default folder on Linux, macOS and Windows.

Fixed

• Turning request dumps off now stops dumping in every running OpenCode process that uses the same config file, at its next request. Before, only the process where you ran the command stopped; the others kept dumping until they restarted (#230). A process started with CORTEXKIT_OPENAI_AUTH_DUMP set still follows that setting.
• On busy machines, a locked account file no longer makes local accounts drop their quota readings. Each process now queues its readings, saves them in batches and retries after a failed save, on OpenCode 1, OpenCode 2 and Pi. When OpenCode or Pi closes, the plugin gives readings still in the queue up to one second to be saved.

Internally, the plugin now uses common-auth 0.26.0. No upgrade steps are needed.