The last post in this series covered getting Claude write access to this site through an MCP plugin. Since then the obvious next step was to make it do something on a schedule without me sitting here: a weekly cloud routine that drafts a “News Roundup” post from Hacker News, LWN, and vendor security advisories, which I review and publish by hand. Getting the sourcing right took two wrong turns worth writing down.
A fix that only worked in the wrong place
The routine’s first run couldn’t reach Reddit at all — r/selfhosted and r/homelab were both meant to be sources, and every fetch came back empty. Testing from my own interactive session, the cause looked obvious: Reddit was returning 403 on a bare curl request, but a plain curl -A "Mozilla/5.0 ..." https://www.reddit.com/r/selfhosted/.rss came back with a real 200 and a working Atom feed. Case closed, apparently — I wired the same curl-with-a-browser-UA trick into the routine’s prompt and called it fixed.
It wasn’t. The cloud sandbox the routine actually runs in sits behind its own policy-enforcing egress proxy, separate from whatever network path my interactive session uses, and that proxy blocks reddit.com outright at the CONNECT level — no User-Agent header gets anywhere near mattering. I only found this by running the routine again on purpose and reading its tool log: curl exit 56, HTTP status 000, and the proxy’s own status endpoint confirming a flat 403 policy denial on the tunnel. Three subreddits, three identical failures. The fix that worked perfectly from my chair had never touched the environment that needed it.
A classifier that wanted to be asked twice
Once Reddit was confirmed dead for good, reverting the routine’s prompt back to the working HN/LWN/vendor-advisories version hit a second wall: the auto-mode permission classifier flatly blocked the config update, no prompt, just a denial. Explaining the situation and getting an explicit “yes, go ahead” was enough to push the same call through moments later — it wasn’t a settings problem, just a case that wanted a human to actually say so first. Trying to add a standing permission rule so that wouldn’t happen again hit the exact same wall, on the exact same terms: blocked cold on the first attempt, fine on the second once I’d confirmed I meant it.
Where that leaves things
The routine now sticks to Hacker News, LWN, and vendor/security advisories, drops Reddit entirely with a note in its own prompt explaining why (so a future run doesn’t waste a cycle re-discovering the same dead end), and creates a draft only — nothing gets published without me looking at it first. The bigger lesson wasn’t about Reddit specifically: a fix verified in one environment is a hypothesis, not a fix, until it’s been proven in the one that actually matters. Sandboxed cloud runs and an interactive terminal are not the same network, even when the code calling into them looks identical.
Leave a Reply