A launchd Job That Fires Once on Deprecation Day, Then Deletes Itself — and the 4 Pitfalls I Hit
This is a follow-up to my earlier post, " Automating a config migration with a one-shot launchd job ." This time the trigger is an external event wi…
Latest News
⚑ Report a ProblemTech news from the best sources
All topics
- игры
AI
Gear
News
Tech
agents
ai
api
architecture
automation
beginners
career
database
devops
javascript
llm
machinelearning
mcp
opensource
performance
productivity
programming
python
react
security
showdev
testing
tutorial
typescript
webdev
3 Wrong Guesses About a Chrome Slot Limit: 3 6 Reserved Lanes
Automation doesn't break when you write it. It breaks in production, weeks later, quietly — and my Chrome concurrency limit broke three separate tim…
Nightly tail-truncation: how I stopped Claude Code's logs from quietly eating my disk
Log files never announce themselves. They just sit there growing until something breaks. This is part of my "Claude Code environment" series — the p…
My Claude Code Logs Ballooned to 22MB — Nightly Auto-Trimming with launchd
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. I…
How Claude Code Detects Its Own Weekly Rot and Repairs Itself
Your Claude Code setup doesn't break in one dramatic moment — it degrades a few bytes at a time, and by the time you notice, you've been paying a co…
Automating a Daily Morning Health Check for Your Claude Code Setup with launchd
In my previous post, Monitoring Claude Code hook watchdogs with launchd , I set up liveness monitoring for hooks — and immediately ran into the next…
Your Claude Code Setup Gets Bloated If You Ignore It — Weekly Auto-Slimming by Watching Injected Bytes, Agent Count, and Frustration Words
This is the next installment in my "Claude Code environment" series. Combined with the idempotent marker implementation from the previous article, I…
Rescuing a Long-Running Job with 'Sub-Step Idempotency' — How vault-auto-ingest Escaped Timeout Hell
This is a continuation of my "Claude Code environment" series. Last time I wrote about making Google Calendar the ground truth for my Vault . This t…
Auto-Retiring Skills You No Longer Use: Weekly Skill Lifecycle Management with launchd
Generating skills automatically is the easy part. Deciding when to throw them away is where everything falls apart. In my last post I covered auto-d…
Retiring a Claude Code Model Unattended with launchd: A Self-Destructing Job That Auto-Patches settings.json
This is another entry in my "Claude Code environment" series. Last time, in Multi-slot launchd retry design , I wrote about the "idempotent morning/…
It Can Die in Its Sleep — Self-Healing launchd Jobs with Multi-Slot Firing and a Done-Marker
My previous piece, " Making a launchd Job Unload Itself ," built a job that runs exactly once and then unloads itself. This time it's the mirror ima…
Auto-Migrating Claude Code with a Throwaway launchd Job — a Script That Deletes Itself When Its Work Is Done
This continues my "Claude Code environment" series that started with showing rate limits live in the status line . This time it's a one-shot model-m…
Is Your 24/7 Automation Actually Alive? Checking It With a Single Command
In my previous autopilot article , I walked through a setup that runs Claude unattended via launchd. This time I want to talk about what happens beh…
Planting a Future Breaking Change Today: A launchd Timer Job That Deletes Itself When Done
This is a follow-up to my earlier post, " Automating a config migration with a one-shot launchd job ." Some breaking changes come with a known expir…