Bonus 8. Everything so far happened inside a folder on your machine. This is how it reaches your cloud storage, your project notes and your generators, and the four questions to ask before you connect any of them.
Your folder. That is genuinely it, and that limit has been doing a lot of quiet work.
Everything in the main course happened in one folder, which is why it was safe to let queues run overnight.
A small bridge that teaches it how to talk to one outside service, and hands it a key.
Once connected, "look at my drive" or "check my project database" become things it can just do, the same way reading a local file is.
The technical name for this is MCP. You will see the acronym in menus and documentation. It stands for a protocol, and knowing that changes nothing about how you use it.
| Connector | What it unlocks |
|---|---|
| Cloud storage | pulling client material in, pushing deliverables out |
| Notes or project database | status, deadlines and specs, without you retyping |
| Your generators | submitting and collecting without a browser tab |
| A browser | reading a page that has no other way in |
The generator one is the big one for you. It is what turns the overnight queue from a nice idea into your actual Tuesday.
The folder was a wall. A connector is a door in it.
Doors are good. You should still know how many you have installed and what is on the other side of each.
A read-only connection is a completely different risk from a read-write one.
Many services let you choose at the point you connect, and most people accept the default, which is usually the broader one.
Connect read-only first. Live with it for a week. Widen it when you hit an actual wall, not in anticipation of one.
"Access to my drive" can mean one folder or everything you own, including things shared with you by other people.
Files shared with you belong to someone else. An automated action there affects their copy, and a deletion is their deletion.
Scope it to a folder if the service lets you. Most do, and almost nobody does it.
The connection is a credential. It is a password with extra steps.
Never paste a key into CLAUDE.md, a skill, a settings file that gets shared, or a chat message. Your secret guard from Bonus 6 exists for exactly this moment.
Keys live where the service tells you to put them, usually a system keychain or an environment value, and they never live in your project.
The unattended queue is the whole point of this system, so the question is not hypothetical.
Sort your connections by that list, and put the bottom two behind ask, permanently, on every posture.
Nothing goes to another person without you approving that specific thing.
Not the category. That message, that file, that share link. Approval you gave on Tuesday is not approval for Thursday.
This is the single rule most worth writing into your CLAUDE.md the day you connect anything that can send.
Some connections should be permanently one-way and never quietly upgraded.
Anything financial. Anything a client owns. Anything that is the only copy.
Write the decision down as a rule, because in six months a task will be slightly easier if you widen it, and that is exactly the moment the decision should already have been made.
Uploading a client's script, footage or artwork to a generative service is itself a disclosure, and most of them retain what you send.
If you work under NDA, this is not a preference. Do the craft problem in the abstract, with your own stand-in material, and keep the real thing off the wire entirely.
Connections accumulate. You will forget the one you set up for a job that ended in March.
"List every connector I have configured, what each can reach, and whether it can write. Flag any I have not used in the last month."
Then disconnect what you are not using. A door you never walk through is still a door.
Without it, an overnight queue means a browser and a person. With it:
"Submit every approved shot, poll until each finishes, download to video/<shot_id>/, log the model, prompt, seed and cost, retry twice, skip anything already downloaded, report at the end."
That is Module 4 of the main course, and this is the piece that makes it literally true.
Same discipline as the main course, and it matters more once a connection can spend without a browser in the way.
"Before submitting anything, tell me how many jobs, and what that will cost at my rate. Show me the total and wait for me. Then stop at that ceiling even if the queue is not empty."
A ceiling and a dry run, every unattended night, forever.
The hardest lesson in the main course lives here too.
A submission that returns success is not a job that exists. Submit one, go and look at it in the service's own interface, and only then release the other thirty nine.
Twenty minutes. Do not connect everything today.
like a credential."*
CLAUDE.md: nothing reaches another person without my approval on that specificthing.
The wall has doors in it now, and you know how many.
Making It Run Without You. Scheduled work, the weekly loop, and health checks that repair instead of just reporting.
Verified against Claude Code 2.1.220 · 2026-07-30.