Repository navigation
Limitcast 0.18.3: settings changes no longer overwrite each other
Two commands that change settings at the same moment no longer lose one of the changes. Every command that writes config.json (budget, plan set, trim keep, models, grok-usage and the rest) used to read the file and write it back, so the later write undid the earlier change when they ran together. Each write now takes a short lock, re-reads the file inside it, and writes through a temp file. A lock left by a killed command is broken after 2 seconds. Hooks only read settings, so they never wait on it.
Details are in the changelog. The audit that named this gap: https://limitcast.dev/blog/limitcast-audit-2026-11-07/