The moment Claude stopped waiting for me
Setting up git push access — and how knowing git made this 20 minutes instead of 2 hours.
For the first few hours, every change Claude made still required me to do something. He'd write the code, and I'd copy it into a file, save it, run a command. Claude was fast. The gap between "Claude done" and "thing actually deployed" was me.
That changed when we set up git push access.
I knew what a Personal Access Token was. I'd set one up before. That prior knowledge made this a 20-minute problem — I knew the words, I knew roughly where to look, and I could explain what I wanted without guessing at terminology. That's the honest context.
But here's the thing: once I explain exactly what to set up and why, you have that knowledge too. That's what this post is for.
The rest is for supporters
Pay once, read everything — this post and whatever comes next.
What's inside
- →The exact token permissions that work — and the ones that silently fail
- →How to store credentials so they never show up in a file Claude can touch
- →The three things that broke the Vercel deploy and the specific fixes
- →What Claude flagged when I made a security mistake before I noticed it