Simon Willison has written about his entire publishing pipeline, which is a wonderful combination of impressive and drop-dead simple. That was one inspiration.
I've also been experimenting with Claude Code Cloud in the last week or two (I think they officially call it “on the web”), inspired by Simon Willison's recent vibespiling posts.
Certain work lends itself to the cloud, I feel like, and there's a lot less prompting there, so you can run and get stuff done with fewer interruptions. Of course, with the trade-off that it might run awhile, going down the wrong track and can make a bigger mess.
The setup: I've got a new dedicated private repo for all my potential content. The goal is for pushes to the
main branch of the repo to auto-schedule posts to my socials via Publer's configured time slots. No more manual copy-paste (not that I was even doing that.)We probably could have knocked this all out in one Claude Cloud session, but we kept running into network blocks trying to work out some details with the Publer API.
The main hangup I think was that network allowlist changes in Claude Code Cloud don't seem to apply to sessions that are already running? I kept getting blocked curl requests even after I added publer.com to the allowlist.
I'm still not 100% sure that was the issue, but eventually I just gave it full network access and started a fresh session, and that finally got things moving.
Once we got past the network stuff, we hit a bug: Publer uses
Bearer-API as their auth header instead of Bearer (which is more common in my experience). There's a typo in their Getting Started example that shows plain Bearer, which is what we ran across first.Claude eventually figured it out by fetching more of the API docs and then just trying different header variations until one actually worked. Kind of a brute force approach but, it got the job done.
#ClaudeCode #Publer #ContentAutomation