Episode 126: Claude Code: Rebuilding 5 Websites Without Writing Code

One of the things I really liked is that you can actually work on multiple projects at the same time, so I was building five different products, websites, rebuilding abandoned websites, just going to one thread, typing something, requesting some changes, and checking out the website.

Hi, my name is Demetri Panici and I'm a content creator, agency owner, and AI enthusiast. You're listening to the AI Agents podcast brought to you by Jotform and featuring our CEO and founder, Aytekin Tank. This is the show where artificial intelligence meets innovation, productivity, and the tools shaping the future of work. Enjoy the show.

Hello and welcome back to another episode of the AI Agents podcast. In this episode, we're going to be talking about Claude Code because it's insane.

I had these websites that I built a long time ago, side projects I abandoned. They were broken because they had old versions of PHP and security bugs, so I decided to give Claude Code a go and I was hooked. It was so easy that I rebuilt five sites and made them much better just by coding without even looking at the code.

I was able to easily deploy them on Vercel, publish them on their own domain names, and it was all free. I was building so much that even though I was on the max plan on Cloud, it told me I was done for the day because I used too much.

I had to stop because I was actually sick, but I was so excited that I was coding for five hours instead of resting. I studied computer science and know how to code, but I haven't coded in 10 years, and it's hard to get back into it.

I never found a large amount of time to work on it, and that's why I said let's do an episode about Cloud Code. At the same time, the same thing happened to you, right? Tell us about your experience.

I've been using it a lot and it's very addicting. I've never been a developer but I've been using it for the last week to develop stuff. I started my journey about a week and a half ago trying it out.

I was using OpenClaw because it has the ability to have automated work, but it's not the builder I want. I had to build up the infrastructure of my OpenClaw setup.

Memoranthropic got rid of the token thing and OAuth connection to OpenClaw and other tools, but Cloud Code was available. I realized my OpenClaw mission control is just a repository coded locally, so I told Cloud Code to edit it.

I backdoored it through the subscription but not through OpenClaw, which is stupid but allowed. I started doing that and then I tried to improve dashboards by connecting APIs and making data work nicer.

I coded something with Cloud Code and suddenly I had that. I was building multiple things at once and tried Lovable connected to GitHub, then moved to the terminal, which we're going to show how easy it is to use.

It even has Vercel access. It's very simple and cool. I'm very excited to show you guys. Long story short, Cloud Code's crazy and both of us realized it not that late considering most people are behind.

I send interactions, and when Cloud Code says you're done, the agent works for me. Then I go to the next step and build another website, just asking it to do something else.

By the time I go back to the first one, it's done. I'm basically giving feedback. At Jotform, I meet with product teams, do reviews, open on mobile, try to use it, and discuss improvements.

That's the same way you can work with Cloud Code. It's like having a team of developers and designers ready to work for you. You just have to know what you want to ask for.

The bottleneck used to be technology or engineers, but now with Cloud Code, the bottleneck is ideas and taste—how to make a great product or website. You focus on value, and the details are handled for you.

I'm not worried about developers losing jobs. They become 10 times more valuable because everyone will build many products needing technological edge and developer help, but developers won't be writing code.

The person who built Cloud Code hasn't written a single line of code since November but built many additions and new products, including the mobile version released yesterday. It's incredible.

I didn't believe it until I experienced it myself. This is an incredible moment in time, but most people aren't aware of this power. You don't have to know how to code; just say what you want and it builds it for you. It's like magic.

It is that simple. To kick things off, let's show an example you built—a website for our podcast.

I built a website for us without writing a single line of code. It's all white-coded. I asked it to go to our YouTube channel and build a website.

It built the website but missed some stuff, so I prompted it to use pictures and create a page with episode summaries and transcripts. I asked it to find better pictures and categorize our podcast into AI healthcare, sales, marketing, and other categories.

Each category shows episodes you can watch or open on a page with breadcrumbs. I want to make an addition now, so instead of sharing that screen, I'll share the entire screen and go to Cloud Code.

How do you find Cloud Code? You install the app on your computer, and it has chat, co-work, and code tabs. You click code and review co-work, which is also incredible. You can probably do everything with Cloud Code that you do with co-work.

People were doing other things besides building, so they built co-work. One thing I do is open a new session to work in parallel. Here you can select plan mode, which I like to start with because I work on multiple things.

When working on multiple things, you want to finish something before starting another to avoid conflicts, especially if changing the same page. I usually work on a plan and ask you to do that plan.

For example, I ask you to add a contact page to the podcast website using Jotform. You can connect to other things; I already connected to Jotform, so it knows my account and can use it.

Even if you don't connect, it can use the Jotform API and work. Let's see what it comes up with. It starts by exploring the codebase to understand the structure and provides a plan.

When I say go ahead and execute, it executes the plan. With Opus, it's kind of slow, but you can use high-key Sonnet, which is faster. Speed isn't a big problem because you can work on other stuff while it works.

I prefer Opus to do it the right way rather than quickly and then ask to fix stuff. When you ask for a plan, it starts asking questions.

It found a contact or feedback form in my Jotform account, but I want to create a new form. It asks if it should be on a separate page or homepage. I say create a contact page.

It says it will create a new Jotform for a separate contact page. I say go ahead, and it builds the form using Jotform's API, updates the index page to add a contact link, and edits files on my computer.

It's much more powerful than Level because it runs on your computer and can install software to use it, so it has more power than something working in your browser.

It's creating a contact form, a contact page, and updating the main navigation simultaneously. It creates a folder and sometimes asks too many questions, but compared to OpenClaw, Cloud Code is safer and more cautious.

When starting out, you want to go fast for prototyping, but once you have a real website or business, you want to be more careful. I completely agree.

It works through a clear plan and shows to-dos on the user interface, making it clear and obvious that work is happening.

The form is ready and pages are created. Opening contact on the browser, the contact link wasn't initially added to navigation, but after refreshing, it appeared in the top navigation.

The first thing I want to change is the form background; it doesn't match the website and needs to be dark themed. I ask it to update the form background to dark.

It uses Jotform's API to do that and completes the update. The form looks better now, but there are two titles, so we might fix that and embed the form differently.

You can connect and integrate with other products using their APIs, which is a big deal. In the app, it's easy to connect and manage connectors and permissions, like read-only for Gmail.

We just updated the page with white coding without looking at the code. It also saves on GitHub, pushing code to GitHub for backup and collaboration.

If you lose your computer or work on another, you can pull code from GitHub and continue where you left off. It's a backup and allows working on different branches.

I created a site project on GitHub and asked it to update the podcast page daily with new episodes and latest update date using GitHub actions, which is free and scheduled daily.

This is incredible because back in the day, you had to automate these things manually. Now you can give automatic ability to find daily episodes, which is wild.

I have multiple terminal instances open, working on many things at once. I set up SSH access to my other Mac Mini, using two different Cloud Code accounts simultaneously.

I open a new Cloud Code instance on my terminal and use commands like 'claude dangerously skip permissions' to code faster by bypassing repeated confirmations.

There are different models like Opus 4.6 and versions with more context, and you can adjust effort levels from low to high. I was using Sonnet, which is a good option.

My projects are running, and I'm getting questions just like you. I have two projects: an ads dashboard with dummy data and AI analysis, and an open Claw mission control synced with Todoist.

I built the ads dashboard in about three days, starting last Thursday and working intensely for two days. It covers Google Ads, LinkedIn ads, YouTube organic, and has filtering and AI analysis.

I use plugins in Cloud Code. I have eight agents working for me doing different tasks, some running for over 21 minutes. You constantly check them and assign new tasks when finished.

Cloud Code released an agent teams feature with a supervisor agent that assigns work to other agents when they're done, so you don't have to manage everything manually.

Plugins I have installed include front-end design, GitHub, Superbase API, Vercel, Figma, Gmail, Google Calendar, and others. Plugins and skills are different; skills are like a repository.

You can discover and add new plugins, like the Superpowers plugin from a YouTube video. People are making great ones all the time.

In the ads dashboard, I used slash superpowers with brainstorm, write plan, and execute plan skills to improve the product and make it look nice with front-end design.

I gave prompts to come up with more ideas for the paid ads dashboard, and it suggested adding meta ads, Facebook ads, keyword research, and more.

It asked about the primary use case, and I said it's both an internal tool for my agency and a SaaS product. I don't want to add more paid ads platforms now, so I let it continue.

My OpenClaw mission control is synced with Todoist, assigning tasks to my team. It outputs spec sheets and docs, and I can make adjustments by typing commands, like moving UI elements.

I improved the content calendar to have board, calendar, and table views, coded with prompts. I just went to bed and woke up to find it done.

It asks which areas are most important, and I prioritized onboarding flow, role-based access, invite teammates, and reporting with exportable PDFs and storage.

Using slash writing plan skill, it gives me a plan, and with execute plan skill, it executes the plan, which is incredible.

It completed many tasks, including adding API keys, copying knowledge files, adding ads creative skills, and upgrading API routes while we were on the call.

I asked it to make a plan to finish wiring up the product, especially creative intelligence, and include ads creative skills for LinkedIn and Google ads with all parameters.

We talked about audio coding and tools like Willow that make writing prompts easier with keybinds, which is a big hack.

I want to ensure new features like creative intelligence work properly and have the right skills, including front-end design.

I like to work in parallel on new pages that don't break existing components, but I never recommend editing connected data in parallel unless you're sure to avoid conflicts.

Keep everything updated on GitHub to prevent breaking things and merge code easily when working on different places. GitHub shows conflicts and helps fix them.

In product teams, multiple developers work on the same files, constantly committing and pulling updates from GitHub to sync their files and fix conflicts.

Cloud Code handles everything, including conflicts. We nerded out about this, and I want to ask where you think this leaves us long term and how it helps you work.

Many people are making skills on co-work, OpenClaw, and Cloud Code, which can be routed to Cloud Code, a tool that can do stuff for a significant period without crashing or losing context.

Cloud Code is a hack, and people should use it over co-work once comfortable. For simple tasks, co-work has recurring automated skills to compete with OpenClaw.

I'm trying to use OpenClaw for recurring day-to-day tasks and build everything using Cloud Code constantly.

This article says Antropics Cloud Code is having a Chip moment, like the first time I spoke to Chip and showed voice conversation to my parents. This is a huge moment for Cloud Code.

We moved to the next level with something working. You can build internal products, websites, or products for others and improve how you work. This is ultimate automation.

We had to cover Cloud Code because it changed things. The future is here now, and we're living in different times compared to 2025.

Consider using Cloud Code or OpenClaw for ultimate automation to save time and brainpower, letting AI handle everything and automate your work.

This has been a longer episode because we got into it. Thanks for watching. Try Cloud Code, hit like, subscribe, and let us know what cool things you're building and what tools you're using.

Thank you for listening and watching, and we'll see you in the next one. Peace.