3 Weeks of Silent Backup Failure: Why launchd Can't Write to ~/Documents on macO

<p>Every night my Mac quietly rewrites my long-term memory. Not metaphorically — a shell script drains that day's Claude Code conversation logs into an Obsidian vault, commits

<p>In earlier posts I walked through <a href="https://zenn.dev/bokuwalily/articles/self-growing-skills" rel="noopener noreferrer">a mechanism that auto-generates skills</a> and <a

<p>In my previous post, <a href="https://zenn.dev/bokuwalily/articles/inject-bytes-watchdog" rel="noopener noreferrer">Monitoring Claude Code hook watchdogs with launchd</a>, I

<p>At 12:04 on August 23, 2026, something quietly rewrote my outreach DM schedule down to three runs a day — 2:31 AM, 10:31 AM, and 6:31 PM. For the several days it took me to

<p>If you've ever built an automated script like a Python crypto price scraper, a daily backup script, or an RSS archiver, you probably felt like a genius right up until the

<h2> TL;DR </h2> <p>My autonomous AI agent runs 34 cron jobs daily. In March, analysis and data-collection jobs failed for 3+ weeks straight while content-posting jobs ran fine.

<p>The same zsh script could list <code>~/Documents</code> when I ran it in Terminal. Started as a LaunchAgent, it failed with:<br /> </p> <div class="highlight

<blockquote> <p>A single Bash script, a USB drive, and 30 seconds a day. No cloud. No subscriptions. No excuses.</p> </blockquote> <p>You have spent months tweaking your Linux