I Let an AI Agent Build My Entire Website While I Lay in Bed
This site was 80% built by AI. Not "AI-assisted" in the vague sense that I used a chatbot for brainstorming. I mean an AI agent literally clicked buttons, filled forms, called APIs, and configured WordPress — while I lay on my back giving instructions through my phone.
The AI was Claude, made by Anthropic. Using its Cowork mode and Chrome extension, it controlled my browser directly: navigating the WordPress admin panel, installing plugins, setting up categories, building navigation menus, configuring theme settings. All through browser automation and REST API calls.
If "WordPress" and "REST API" sound intimidating, that's exactly the point. They used to be barriers. Now the AI handles them, and you just describe what you want.
Why I Needed an AI to Do This
Quick context. I'd spent years in corporate HR at a large company. Then a herniated disc made sitting at a desk physically impossible. Sciatica so severe that using a computer in a normal position was out of the question.
"Build a blog" seemed like a reasonable project for someone stuck in bed. The problem was that building a WordPress site involves dozens of hours of configuration work — theme customization, plugin setup, SEO settings, navigation structure, analytics integration. All of it requires sitting at a computer and clicking through admin screens, one setting at a time.
Sitting was the one thing I couldn't do. So instead of building the site myself, I told an AI to build it for me.
What the AI Actually Handled
The scope of what Claude's Cowork mode did automatically was broader than I'd expected going in.
It controlled my browser through the Chrome extension — navigating to settings pages, clicking toggles, filling in fields, saving configurations. What would have been hours of manual clicking through WordPress admin screens took minutes of automated execution. When I needed four pages created (About, Services, Contact, and one more), Claude skipped the admin panel entirely and called the WordPress REST API directly, creating all four in seconds. Same for blog categories — three categories, created via API, done in moments.
The theme configuration was where automation really showed its value. I'd chosen SWELL, a popular Japanese WordPress theme. Claude configured colors, layout options, and branding through the theme's customizer API. No manual adjustment, no squinting at font dropdowns, no previewing and re-previewing. It also handled navigation menus — header and footer, with proper page assignments — and configured plugins for SEO (SEO SIMPLE PACK), security (XO Security), and comments. Each plugin's settings were optimized without me touching the admin panel.
Google Analytics integration was another task I'd been dreading. Claude handled the Site Kit setup process end to end. The only thing I did was tap "Allow" on my phone when Google's OAuth screen appeared. After that, it verified permalink structures, removed default categories, and did a general cleanup pass on the WordPress configuration.
All told, the AI handled roughly 80% of the setup labor.
What Only a Human Could Do
The remaining 20% fell into a very specific pattern. I signed up for Xserver (a fast, WordPress-optimized Japanese host) because the server contract required my payment information. I purchased the SWELL theme because that required a transaction. I completed SWELL's owner verification because the theme requires human authentication. I tapped "Allow" during Google's OAuth flow. And I read and agreed to terms of service.
Authentication. Authorization. Payment. Legal consent. That's the boundary. Everything that requires proving you're a human, or committing to a legal agreement, stayed on my side. Everything else — the actual configuration work, the clicking and setting and building — was fully automated.
What AI Got Wrong
I want to be transparent about this part, because "80% automated" can sound like it means "80% correct." It doesn't.
Claude created article drafts that didn't match what I had in mind. Technical information was wrong in places. One section was duplicated three times. The theme configuration looked slightly different from what I'd described. Every output required human review.
AI automation isn't "set and forget." It's "delegate and verify." The analogy I keep coming back to is managing a junior team member: you trust them to handle the bulk of the work, but you check every deliverable before it goes live. The speed advantage is enormous. The quality assurance requirement doesn't go away.
This is worth being honest about because the narrative around AI often swings between two extremes — either "AI can do everything" or "AI is unreliable garbage." The reality, at least for building a WordPress site, is somewhere in between: it handles the mechanical work beautifully, and it needs a human eye on the output.
Why This Matters Beyond My Situation
"A guy with a herniated disc used AI to build a WordPress site" could sound like a niche tech story. I don't think it is.
What happened here is a preview of how software setup is going to work going forward. The pattern is straightforward: a human decides what they want, handles authentication and legal decisions, and an AI handles everything else. This applies to anyone who's ever been intimidated by technical setup — and that's most people.
You don't need to know what a REST API is. You don't need to understand WordPress's admin panel structure. You describe what you want, and the AI figures out how to make it happen. Five years ago, if you couldn't sit at a computer, building a website was impossible. Today, the physical constraint is irrelevant — because the person directing the build doesn't need to be physically present at a keyboard.
That shift is bigger than one website. It means the barrier between "having an idea" and "having a live website" has collapsed to something close to zero for anyone willing to review AI output and make decisions. The labor bottleneck is gone. What remains is judgment, taste, and the willingness to ship something imperfect.
Constraints Breed Innovation (But Not the Way You'd Expect)
This site is called "Gorone Survival" — roughly, "surviving while lying down." The AI-assisted build process isn't just a technical detail. It's the site's concept made real.
I couldn't sit. So I found a way to build without sitting. The tool happened to be an AI agent, but the principle is older than any technology: when one path closes, you look for another.
What's new is that the "another" actually exists now. Voice input, AI agents, browser automation — these aren't future promises or demo-stage prototypes. They're what I used to build the site you're reading right now, lying flat on my back, talking into a phone.
If Something Is Stopping You From Building
If health, circumstance, disability, or time constraints are keeping you from creating something you want to create, I'd ask you to reconsider what's actually required.
The barrier to launching a website, a blog, a portfolio, or any kind of online presence has dropped further than most people realize. Not in a marketing-brochure way. Concretely — to the point where someone in a hospital bed can do it with voice commands and an AI agent.
You still need to make decisions. You still need to review what the AI produces. But the physical labor of clicking through settings screens, configuring plugins, and building page structures? That part is optional now.
Start by telling an AI what you want to create. Don't worry about the technical details. Describe the outcome. You might be surprised how much of what felt impossible simply disappears.
Written by Ryo — years in corporate HR, herniated disc survivor. This site was built using AI agents (Claude Cowork mode). All content reflects my own experience and is not technical advice.
Read next:
- How I Rebuilt My Work Life From Bed Using Only My Voice
- I Spent 1,500 Hours Talking to AI From a Hospital Bed