Put the Work Where the Agent Can Reach It

Three weeks ago I wrote that Claude’s scheduled tasks run in the cloud but can’t reach a folder on my Mac. My whole newsletter studio lived in that folder. Every draft, every status file, every lesson. On October 17 I moved all of it out.

The Insight

The studio worked. An operating manual, nine skills, guard scripts, and plain-text files that tracked where each piece stood. Claude Code ran it well, as long as the Mac was on and I was sitting at it.

The folder was the bottleneck, not the tools. A cloud agent can read Notion, GitHub and Google Drive. It can’t read my hard drive. So the one place that held the whole operation was the one place the agent couldn’t open.

The Fix

I split the studio by what each part is.

Content and rules went to Notion: 26 pieces, 19 distribution records, 22 learning pages, 75 reference pages and 105 working files. The status file, the board and the run log stopped being text files. They’re database fields now.

The engine went to a private GitHub repo. Image renders and website screenshots run in GitHub Actions, on GitHub’s machines instead of mine. First CI run, green. First screenshot run, green. A test render went from draft to Drive without me touching it.

Media went to Google Drive, and deliberately not to git. Git stores a snapshot every time something changes and keeps them all. A weekly set of carousel images would sit in the repo’s history for good. Only small brand files that rarely change stay in the repo.

The approval step moved too. Publishing used to need a terminal script I ran by hand. Now it needs my yes in chat. Same gate, no laptop required.

One step went wrong. Connecting Drive meant running rclone’s setup command, and it printed the access token straight into the terminal. I pasted that log into a chat to debug something else, token and all. The key is now on the reset list. The new rule: any command that creates a credential sends it straight to a secret store and never prints it.

The Hard Truth

The move cost me something real. The old studio had code guards: hooks that blocked deletes, overwrites, and any attempt by the agent to approve its own publishing. They were tied to Claude Code on the Mac, so they’re retired. What replaced them is a written playbook and three gates that only open on my yes.

A written rule is cheaper to change than a code guard. It’s also easier to break. So the playbook carries one more rule about rules. If a lesson comes back after it became a rule, the rule failed, and it goes back into the repo as a check.

Things don’t have to be perfect. They have to be somewhere the work can reach them.

Sources

• Claude scheduled tasks run in the cloud but can't be tied to a folder on the computer — Claude Help Center
• Git stores data as a series of snapshots, one per commit — Pro Git
• GitHub-hosted runners are virtual machines GitHub hosts to run workflows — GitHub Docs