Posts

Showing posts from September, 2026

Running Multiple Claude Code Sessions on One Project: What I Split, What I Shared, What Broke

Image
Since September 30, 2026, I've had two Claude Code sessions working in the same project folder at the same time. One handles my blog workflow. The other is building a new YouTube channel. I'm not a developer, and I talk to each one in its own window. People search for "multiple Claude Code sessions" with all kinds of follow-ups: at once, in parallel, can they talk to each other. Here's what a day and a half of actually doing it taught me. It's a short track record, so treat this as field notes, not a benchmark. Why I opened a second session The blog had a steady routine: research, draft, review, publish. The video channel needed something different: scripts, voice, an assembly pipeline. Doing both in one conversation would have mixed two very different jobs into one long context. So I asked how to run the video work "in another window," and set one up. Photo: Hatice Baran on Pexels Same folder or separate copy? Claude Code can work in an is...

AI Agent Approval: How I Let My Agents Publish on Their Own, and the One Switch I Kept

Image
I run my side projects with AI agents. They research topics, prepare drafts and images, fact-check, and publish to my blog. Until September 30, 2026, the one thing only I did was click "approve." That day I asked for that to go too: approve it yourselves and just post it. This post is about how I designed that permission, what the approval step had actually caught, and the one control I refused to automate. The request: "just post it yourself" I'm not a developer. Every post needed two clicks on my dashboard, and I wanted the agent to handle those too. The first attempt failed in an instructive way. My main agent (Claude Code) tried to record the approval on my behalf, and the agent tool's own safety check blocked it . It treated an agent writing a human's approval as something it shouldn't do alone. The same check blocked two more steps that day. In the end, I had to edit the tool's permission allow-list myself before the new setup could b...

Which AI to Use for What: A Task-by-Task Guide From a Week of Working With Claude, ChatGPT, and Gemini

Image
"Which AI should I use?" is the wrong first question. After a week of handing most of my project work to AI agents, the better question turned out to be: what's the task, and what does it need? I pay for three ordinary consumer subscriptions, Claude, ChatGPT, and Google's AI plan, and I've ended up assigning work by task, not by brand. Here's the table I actually use, what each assignment is based on, and what I do when one tool runs out of room. Measurements below come from my own accounts during September 26–30, 2026. Your plan, timing, and tasks may give different numbers. Start from the task, not the tool Every job in my workflow falls into one of a few types. For each type I ask three things: does it need long, careful multi-step work? Does the output need exact text? Is speed or cost the constraint? Task My pick Why Research, drafting, reviewing, record-keeping Claude (Claude Code) Follows a long rulebook across many steps; does the bulk of my wor...

Blogger Custom Domain HTTPS: Why the Padlock Took Days, and the Switch That Took My Blogs Offline

Image
I connected two Blogger blogs to my own subdomains on September 26, 2026. The blogs loaded over http:// within about 15 minutes of adding the DNS records. The padlock ( https:// ) didn't show up that night, or the next day. Here's what was actually wrong, the switch I flipped too early (which briefly took both blogs offline), a side effect that confused my publishing script, and the order I'd follow next time. The timeline When (2026, local time) What happened Sep 26, 20:30 Added the CNAME records at my domain registrar and saved the custom domains in Blogger Sep 26, 20:44 Both blogs loaded over http:// . https:// failed to connect Sep 27, ~21:15 Found the cause in Blogger settings and turned on HTTPS availability Sep 27, ~21:15 Also turned on HTTPS redirect . Both blogs stopped loading for everyone. Turned redirect back off Sep 30, 02:31 Checked again: https:// loads on both blogs I didn't check between the evening of Sep 27 and early Sep 30, so I can only say ...

I Switched From Claude Code to Codex: The Project Files That Preserved Context

Image
I built my local work system with Claude, then opened the same workspace in Codex. The first thing I wanted to know: “How did Codex find everything Claude made—and can Claude take over again later?” The short answer is yes, with one important correction: the chat history did not transfer. The project state did. Codex read the files Claude had left in the workspace: operating rules, task history, decisions, failure notes, role workflows, and a local database. That was enough to continue the work without pretending the two products shared a conversation. Here is the structure that made the handoff work, what still did not carry over, and the rules I now use before switching agents. What survived the switch The durable part of my setup lives outside any single chat. Shared source Purpose AGENTS.md Tells Codex which instructions to follow CLAUDE.md Holds the overall operating rules skills/ Stores repeatable role and workflow instructions A decisions file Records the decisions I'...

Automating Blog Posts With AI, Safely: What the Blogger API Can't Do (and My Workarounds)

Image
For my first few posts, publishing meant copying HTML from my dashboard and pasting it into Blogger by hand. It worked, but it was slow and error-prone: once, the wrong page's text ended up on my Privacy Policy. So I automated it with Google's official Blogger API. Now I do one thing: click Approve . Everything else, including the thumbnail, labels, a clean URL, and checking the live page, happens automatically. Here's how it works, the two things the API can't do, and one mistake that briefly took my blogs offline. Rule one: no approval, no post Before anything else, the publishing script checks my dashboard's approval records for that task. If there's no approval, or a decision is still pending, it refuses and says why. It also refuses to publish the same draft twice. I tested both refusals before the first real run. If you automate publishing, build the "no" path first. Photo: Andrew Neel on Pexels The one-time setup (about 15 minutes) Cre...

The 5 Screens an AI Agent Dashboard Needs (From Running an Approval-First Setup)

Image
I run a handful of AI agents for my side projects, and I don't write code. That combination creates one hard requirement: nothing goes public until I click Approve , and I should never need a terminal to do it. So on day one I had a small local web dashboard built (by an AI coding agent) with exactly that job. It runs only on my own PC. After a day of real use, including one rejected approval and a couple of mistakes, here are the five screens I'd insist on again, and what each one taught me. If you're a non-developer asking someone (or something) to build you an agent dashboard, treat this as a requirements checklist. 1. A task board with honest statuses Every instruction becomes a numbered task that moves through seven states: waiting, in meeting, working, in review, awaiting approval, done, failed . Why seven and not "to do / done"? Because the dangerous moment is the gap between "the agent thinks it's finished" and "a human has signed ...

Day One With an AI Agent Team: 6 Things That Broke (and the Fixes)

Image
On September 26, 2026, I set up a small team of AI agents on my PC. Claude does research, writing, and review. OpenAI's Codex and Google's Antigravity make images. I don't write code. Most setup guides show the happy path. This post is the other half: the six things that actually went wrong on day one, why they happened, and what I changed. Every item comes from my own failure log, so none of this is hypothetical. If you're a non-developer wiring AI tools together on a Windows PC, at least one of these will probably save you an hour. 1. The image tool had no quota left before I started What happened. My first image request to Codex failed instantly with "You've hit your usage limit," and a time when it would reset. Why. Codex usage on a ChatGPT plan is shared across the places you use it. OpenAI says the same limits apply in the app, the CLI, the IDE extension, and the cloud ( OpenAI Help Center , checked 2026-09-26). I hadn't run anything thro...