It has been well over a year since my first (and only) post.

You know how it goes. You get excited about a tech stack, you spin up a Next.js project, you obsess over Tailwind classes, you deploy it to Vercel, and you write that inaugural "Hello World" post. You feel like a publisher. I will definitely be writing interesting things that world has to hear on my blog every week...nay, every day!

And then... nada.

The problem with building a blog engine is that once you've built, you actually have to do the writing. And frankly, I’ve been busy driving El Bólido Rojo and enjoying life.

But today, I decided to cheat. I brought in backup. I fired up the Gemini CLI agent to help me get back on track.

The Plan

The goal was simple: get Gemini to write and upload a post for me. But as with all things software engineering, "simple" quickly turned into "let's refactor the authentication layer."

The Hurdle: Read-Only Access

My blog fetches data from Hygraph (formerly GraphCMS). The existing setup was perfect for reading posts—it used a public Content API endpoint. But when I asked Gemini to "just add a post," we hit a wall.

Mutation failed due to permission errors

We were trying to write to the database using a read-only door. We needed a key.

The Fix: Permanent Auth Tokens (PAT)

To let the agent post on my behalf, we had to set up a Permanent Auth Token in Hygraph. Here is how we did it:

Hygraph Dashboard: Went to Project Settings > API Access.
Create Token: Generated a new PAT.
Permissions: This was the crucial part. By default, tokens often just have Read access. We had to specifically enable Mutations for the Post model (Create, Update, Publish) and, importantly, the Asset and Author models so we could link images and authors to the post.
Environment Variables: We added the HYGRAPH_TOKEN to the local .env file.

Security Side Quest

In the process, we realized a rookie mistake: my .env file was being tracked by Git! 😱

Before adding the secret token, Gemini (very politely) yelled at me. We had to stop tracking it, update .gitignore, and commit the security fix.

The Result

With the token secured and the permissions granted, we wrote a Node.js script that shoots a createPost GraphQL mutation directly to Hygraph.

So, if you are reading this... it worked. The robot is writing, the CMS is accepting it, and I can go back to driving my new car. Good work Gemini. Good work. 🤖