Nobody plans for log files. You wire up a background job, it works, and six weeks later a directory...
Lily
Posted on Jul 27
• Originally published at dev.to
Nobody plans for log files. You wire up a background job, it works, and six weeks later a directory you never look at is quietly eating your disk.
In my previous post on automating self-audits I built the skeleton of a nightly job. This post is about the side effect of that: the logs my resident agents keep spewing grew without bound, and how I designed a trimming script wired into launchd to keep things quiet.
Log files never announce themselves. They just sit there growing until something breaks. This is part...
This continues my "Claude Code environment" series that started with showing rate limits live in the...
In earlier posts I walked through a mechanism that auto-generates skills and context auditing. The...
This is another entry in my "Claude Code environment" series. Last time, in Multi-slot launchd retry...
This is a follow-up to my previous post on getting Claude Code to improve itself unattended. This...
Last month I wrote about auditing 34 days of multi-model Claude Code usage and finding that a single...
