# CatDoes Cloud Source: https://docs.catdoes.com/catdoes-cloud The backend infrastructure that powers your CatDoes apps — automatically configured through AI. ## Overview CatDoes Cloud is the managed backend that runs behind every app you build. You don't need to set up servers, databases, or authentication manually — CatDoes configures everything through your natural language prompts. ## What's included A managed database for your app's data. CatDoes creates tables, relationships, and queries based on your app's requirements. User sign-up, login, and session management — configured automatically. Supports email/password, social logins, and more. File and media storage for user uploads, images, and app assets. Managed and scaled for you. Serverless functions for custom backend logic, webhooks, and third-party integrations — deployed at the edge for low latency. ## How it works When you describe your app, CatDoes automatically provisions the backend resources you need. For example: * "I need users to sign up and log in" → authentication is configured * "Users can upload profile pictures" → storage bucket is created * "Show a feed of posts" → database table and API endpoints are set up You can also make changes later by describing what you need in conversation, and CatDoes Cloud updates accordingly. CatDoes Cloud is fully managed. You don't need to worry about scaling, backups, or infrastructure maintenance. # Base44 to Native App Source: https://docs.catdoes.com/features/base44 Convert your Base44 website into a native iOS and Android app. Base44 generates standard web applications using React and Tailwind. To get them onto mobile, most wrapping tools place your site inside a **WebView** — an embedded browser that makes the web app *look* native but still runs through a browser engine. This adds latency, blocks access to hardware features like Bluetooth, NFC, Face ID, and real push notifications, and often gets rejected from the App Store for not offering functionality beyond a website. A true native app talks directly to the operating system's UI components with no browser layer in between, which is what CatDoes builds for you. There are two ways to convert your Base44 website into a native app. Pick whichever works best for you. ## Method 1: Using Your Website URL Best for public-facing websites where all pages are visible without logging in. 1. Visit [catdoes.com](https://catdoes.com) and enter your Base44 website URL. 2. Log in to CatDoes — the system automatically detects your website. 3. Choose whether to make your project **Public** (free) or **Private** (requires subscription). 4. CatDoes analyzes your website, extracting: * Design elements and color scheme * Branding (logo, fonts, icons) * Content from your pages * Screenshots for reference 5. The AI agent creates your mobile app specification based on your website's design. 6. The software agent builds your native iOS and Android app. Your website is analyzed automatically. You don't need to provide any design files or assets — everything is extracted from your live site. ## Method 2: Import via GitHub Best when your Base44 website has pages behind a login — like dashboards, account pages, or admin panels — that the agent can't see by visiting the URL. By importing through GitHub, the agent gets full access to your entire project and can rebuild every part of your app accurately. ### Step 1: Connect Base44 to GitHub 1. If you don't already have a GitHub account, go to [github.com](https://github.com) and sign up — it's free and only takes a minute. 2. In your Base44 project, go to the **GitHub** section and connect your project to a repository. Base44 will push your project's code to GitHub automatically. ### Step 2: Import into CatDoes 1. Go to [app.catdoes.com](https://app.catdoes.com/dashboard) and click **Create New App**. 2. Choose **Import from GitHub**. 3. Authorize CatDoes to access your GitHub account and select the repository that contains your Base44 project. 4. Pick the branch you want to import (usually the default one is fine). 5. Give your project a name and click **Import**. CatDoes will pull in your entire project and set everything up. Once the import is done, the AI agent has full access to all your code — including pages that were behind a login — and can start building your native mobile app from there. ## After Conversion Once your app is created, you can: * Preview it in your browser or with [Expo Go](/features/live-preview) * Continue refining with the AI agents * Deploy to [web, Android, or iOS](/features/deployment) The conversion process captures your website's current state. After conversion, you can ask the AI agents to customize the app further or add mobile-specific features like push notifications, offline support, or native gestures. # Checkpoints Source: https://docs.catdoes.com/features/checkpoints Every new chat saves a snapshot of your project so you can roll back anytime. ## What Are Checkpoints? Every time you start a new chat, CatDoes automatically saves a checkpoint — a snapshot of your project at that moment. If something goes wrong in a later chat, you can roll back to any previous checkpoint and pick up from there. Think of it like save points in a game. Each new chat is a new save. If things don't work out, you can always go back. ## How It Works 1. You're working on your project in a chat. 2. You start a new chat — CatDoes saves a checkpoint of your project's current state. 3. You keep building in the new chat. 4. If something breaks or you don't like the direction, you roll back to the checkpoint from before that chat started. You don't need to do anything extra — checkpoints are created automatically whenever you start a new chat. ## When to Start a New Chat Since each new chat creates a checkpoint, starting a new chat is also how you create a save point. Some good moments to do that: * **After finishing a feature you're happy with.** Start a new chat so that state is saved. * **Before trying something risky.** About to experiment with a big layout change or a new feature? Start a new chat first so you can roll back if it doesn't work out. * **When the conversation gets long.** Long chats can cause the agent to lose track of earlier context. Starting fresh gives you a clean slate and a save point. ## Rolling Back To roll back to a previous checkpoint: 1. Click on **History** in the chat panel. 2. Browse and select the chat you want to roll back to. 3. Click **Revert to this point** to restore your project to that checkpoint. Your project will return to the exact state it was in when that chat started. This means you can experiment freely — try bold changes, test ideas, let the agent go in a new direction — knowing you can always undo it all in one step. ## Tips * **Start a new chat when you're happy.** If your project looks good right now, start a new chat to lock that in as a checkpoint. * **Don't be afraid to experiment.** Checkpoints mean you can always undo. Try things out without worrying about breaking what you've built. * **Roll back instead of fixing.** If the agent went in the wrong direction and the result is far from what you want, rolling back and re-prompting is often faster than trying to fix it piece by piece. # Custom Domain Source: https://docs.catdoes.com/features/custom-domain Use your own domain name for your deployed web app. When you deploy your project, CatDoes gives you a free URL like `yourapp.catdoes.app`. If you want to use your own domain instead (like `www.yourcompany.com`), you can set that up too. ## How It Works ### Step 1: Deploy Your Project First, ask the AI agent to deploy your project. Just tell the agent something like "I want to deploy my project" and it will walk you through picking a URL and getting your app live at `yourapp.catdoes.app`. If you haven't deployed yet, check out the [Deployment](/features/deployment) page for more details. ### Step 2: Ask for a Custom Domain Once your project is deployed, tell the agent you want to use your own domain. For example, you can say "I want to use my custom domain" and the agent will guide you through the setup. ### Step 3: Set Up Your Domain You'll need to go to wherever you manage your domain (like GoDaddy, Namecheap, Google Domains, Cloudflare, or any other provider) and point it to your CatDoes app. Here's what to do: 1. Log in to your domain provider. 2. Find the **DNS settings** for your domain. 3. Add a new **CNAME** record: * **Name/Host**: your domain or subdomain (for example `www` or `app`) * **Value/Target**: `yourapp.catdoes.app` (replace `yourapp` with the slug you chose during deployment) 4. Save the changes. DNS changes can take a few minutes to a few hours to take effect, depending on your domain provider. ### Step 4: Come Back and Confirm Once you've set up the DNS record, go back to CatDoes and let the agent know. The agent will verify the setup and get your custom domain connected. ## Tips If you're not sure where your DNS settings are, search for "DNS settings" in your domain provider's help pages — every provider has them, they're just in different places. You can always keep using your `yourapp.catdoes.app` URL even after setting up a custom domain. Both will work. # Debug Mode Source: https://docs.catdoes.com/features/debug-mode How to prompt the agent to find and fix bugs in your project. ## When Something Breaks When you hit a bug, tell the agent to enter debug mode. The agent will add console logs throughout the relevant code, and then you reproduce the broken flow on your device. The logs give the agent real output to inspect — making it much easier to pinpoint what's broken and where. Here's the prompt: > "Enter debug mode: add logs wherever necessary, I will redo the broken flow on my device so the logs appear for you to inspect. Giving more insight into what's broken and where the bug is." ## The Flow 1. **You prompt debug mode.** Tell the agent what's broken and ask it to add logs. 2. **The agent adds logs.** It reads through the relevant code and places console logs in the areas that matter. 3. **You reproduce the bug.** Redo the broken flow on your device so those logs fire. 4. **The agent inspects and fixes.** With real log data, the agent can see exactly where things went wrong and apply the fix. You don't need to know where the bug is — you just need to trigger it. The logs do the talking. ## Give Context The more you tell the agent about the problem, the better it knows where to place logs. Include: * **What's broken** — what you see happening (or not happening). * **What you expected** — what should have happened instead. * **Any extra context** — when it started, what changed recently, or any error messages you see. For example: > "Enter debug mode. The contact form stopped submitting after we added the new header. Add logs to the form submission flow — I'll try submitting again and share what comes back." > "Debug mode. The checkout page crashes when I click pay. Here's the error I'm seeing: \[paste error]. Add logs around the payment flow so I can reproduce and get more detail." ## Use Screenshots with Markers If the bug is visual, take a screenshot and mark the problem area with a red circle or arrow. Upload it with your debug prompt: > "The section I circled in red is overlapping the footer. Enter debug mode and add logs — I'll reload the page and share the output." A marked screenshot removes all ambiguity — the agent can see exactly what you're looking at. Use any basic markup tool (your phone, Preview on Mac, Paint on Windows, or any screenshot tool) to draw on the screenshot before uploading. ## Share Error Messages If you see an error message — in the preview, in a popup, or in your browser's developer console — paste it directly into your prompt. Error messages help the agent know exactly where to place logs and often point straight to the root cause. > "I'm getting this error when I submit the form: `TypeError: Cannot read property 'email' of undefined`. Enter debug mode, add logs around this, and I'll reproduce it." ## Tips * **Say "debug mode."** This signals the agent to investigate thoroughly — read the code, add logs, and prepare for you to reproduce the issue. * **Mention what changed.** If something broke after a recent edit, say so. It helps the agent place logs in the right spots. * **One bug at a time.** If you have multiple issues, debug them in separate prompts. This keeps the logs focused and leads to cleaner fixes. * **Always share the log output.** The whole point of debug mode is the back-and-forth — the agent adds logs, you reproduce, and the logs reveal the problem. * **Don't worry about being technical.** You don't need to understand the code. Just describe what's wrong, reproduce the flow, and paste what you see. # Deployment Source: https://docs.catdoes.com/features/deployment Deploy your CatDoes app to the web, Android, and iOS. When your app is ready, just tell the agent where you want to release it — for example, *"I want to release my app to the App Store"* or *"Deploy my app to the web."* The agent takes care of the rest, walking you through each step right in the chat. ## Web Deploy your app to a `*.catdoes.app` URL and share it with anyone. 1. Tell the agent you want to release your app for the web. 2. Pick a short URL slug for your app (e.g., `myapp` becomes `myapp.catdoes.app`). 3. CatDoes builds and deploys your app — you'll get a live link when it's done. You can change your slug later. The old URL is automatically cleaned up. **Slug rules:** 1-30 characters, lowercase letters, numbers, and hyphens only. Free-plan web deployments include a small "Powered by CatDoes" badge. ## Android Build your app for Android and publish it on Google Play. 1. Tell the agent you want to release your app for Android. 2. A secure input field appears for your Expo token — the agent guides you through creating one if you don't have it yet. 3. Confirm your app version and choose a build type. 4. CatDoes builds your app — this usually takes 10 to 30 minutes. 5. Once the build is ready, you can download it and publish it on Google Play yourself. Android releases require a paid plan and an [Expo](https://expo.dev) account. ## iOS Build your app for iOS and submit it to the App Store. 1. Tell the agent you want to release your app for iOS. 2. Secure input fields appear for your Expo token and your Apple Developer credentials — the agent guides you through setting these up if it's your first time. 3. Confirm your app version and CatDoes starts the build — this usually takes 10 to 30 minutes. 4. When the build is done, you can ask the agent to submit it directly to the App Store. 5. From there, you decide on Apple's side whether to release it through **TestFlight** for testing or make it available publicly. iOS releases require a paid plan, an [Expo](https://expo.dev) account, and an [Apple Developer](https://developer.apple.com) account. Your credentials are entered through secure input fields that encrypt everything you type. The AI never sees your actual tokens or passwords — it only knows whether they've been provided or not. # Free Credits Source: https://docs.catdoes.com/features/free-credits Ways to earn free CatDoes credits — from sharing on X to community programs. ## Share on X You can earn up to **500 free credits** by sharing your CatDoes project on X (Twitter). Look for the free credits option in your dashboard to get started. ## CatDoes Catapult CatDoes Catapult CatDoes Catapult is a monthly program where we hand-pick users and give them **free credits and hands-on support**. Every month, we select builders based on what they're working on — whether it's a side project, a startup, or something experimental. If you're selected, you'll receive free credits to keep building plus direct support from the CatDoes team to help you move faster. **How to apply:** 1. Join the [CatDoes Discord](https://discord.com/invite/g9zaWq5wby). 2. Introduce yourself in the **#introduction** channel — tell us who you are and what you're building. 3. Fill out the [application form](https://forms.gle/Fosvjp4otA7VxspZ6). We review applications each month and reach out to selected users directly. ## Cat Composer Cat Composer Cat Composer is a special role we give to active members of the CatDoes Discord community. If you're regularly helping others, sharing feedback, or contributing to discussions, you may be selected to become a Cat Composer. **What you get as a Cat Composer:** * **Free monthly credits** to use on your projects * **Early access to experimental features** before they're available to everyone * **Direct access to the founders** — ask questions, share ideas, and get support straight from the team Join the [CatDoes Discord](https://discord.com/invite/g9zaWq5wby) and get involved to be considered. # GitHub Integration Source: https://docs.catdoes.com/features/github-integration Connect your GitHub repository so AI agents can read your code, make changes, and push updates directly. Connect your CatDoes project to a GitHub repository. Once connected, AI agents can read your existing code, make changes, commit them, and push updates to your repository — all while maintaining full git history. GitHub integration requires an active paid subscription. ## Connecting Your Repository 1. From your project dashboard, click **Connect GitHub**. 2. On GitHub, authorize the CatDoes app and select which repositories to grant access to. 3. Back on CatDoes, select the repository you want to link from the dropdown. 4. Choose the branch you want to work with (defaults to your repository's default branch). 5. Click **Link Repository**. Your GitHub integration is now active. AI agents can now read, modify, and push code to the selected branch. ## Working with Branches You can switch branches or create new ones directly from your project dashboard. **To switch branches:** 1. Click **Change** next to your connected repository 2. Select a different branch 3. Click **Update** **To create a new branch:** 1. In the branch dropdown, click **Create New Branch** 2. Enter a branch name (like `feature/new-feature` or `fix/bug-name`) 3. Optionally select which branch to create it from 4. Click **Create** The new branch is created on GitHub and immediately available for use. ## How AI Uses GitHub When you ask an AI agent to make changes: 1. The agent reads your existing code from the connected repository 2. Makes the requested modifications 3. Commits the changes with a descriptive message 4. Pushes to your selected branch All changes are tracked in your git history, just like regular commits. The agent can also: * Pull the latest changes from GitHub before making modifications * Handle merge conflicts if they arise * Reset to the remote state if needed ## Changing or Disconnecting **To change repository or branch:** 1. Go to your project dashboard 2. Click **Change** on the GitHub Integration card 3. Select a new repository and/or branch 4. Click **Update** **To disconnect:** 1. Go to your project dashboard 2. Click **Disconnect** on the GitHub Integration card Disconnecting removes the link but doesn't affect your repository on GitHub. ## Tips Work on feature branches instead of main. This keeps your main branch stable while letting the AI experiment on separate branches. Review AI commits on GitHub after they're made. Check the diff to see exactly what changed and why. # Import from GitHub Source: https://docs.catdoes.com/features/import-from-github Bring an existing GitHub project into CatDoes and let AI turn it into a mobile app. Already have a project on GitHub? You can import it directly into CatDoes instead of starting from scratch. This is a great way to bring in projects from tools like Lovable, Bolt, or any codebase you already have on GitHub. Importing from GitHub requires a Plus plan or above. ## How to Import 1. Go to [app.catdoes.com](https://app.catdoes.com/dashboard) and click **New Project**. 2. In the dialog, click **Import from GitHub**. 3. You'll be taken to GitHub to authorize CatDoes. Choose which repositories you want to give CatDoes access to, then confirm. 4. Once you're redirected back to CatDoes, the import form opens automatically. 5. Select your **repository** from the dropdown. 6. Choose the **branch** you want to import (your default branch is selected automatically). 7. Give your project a **name** — it's auto-filled from your repository name, but you can change it. 8. Choose your project visibility: * **Public** — anyone can see your project. Free to create. * **Private** — only you and your team can see it. Requires an active subscription. 9. Click **Import**. CatDoes will pull in your code and set everything up. Once it's done, you're taken straight to your new project, ready to start working with the AI agents. ## When to Use This * You built something with **Lovable**, **Bolt**, or another tool and want to turn it into a native mobile app * You already have a codebase on GitHub and want AI agents to work with it * Your project has pages behind a login that CatDoes can't access by visiting the URL directly — importing the code gives the agent full access to everything ## Tips If your project isn't on GitHub yet, most tools (like Lovable) let you connect to GitHub with a few clicks. Once your code is pushed there, you can import it into CatDoes. After importing, your project is linked to the GitHub repository. You can manage the connection from your project dashboard — see [GitHub Integration](/features/github-integration) for details. # Live Preview Source: https://docs.catdoes.com/features/live-preview Preview your app in real time as you build it with CatDoes. ## Browser Preview As you build your app with CatDoes, a live browser preview appears in a panel alongside your conversation. Every change the agent makes — new screens, design tweaks, feature additions — is reflected in the preview automatically. ### Auto-Refresh The preview refreshes automatically when: * The agent finishes writing or modifying code files * A codebase scan completes * The agent explicitly reloads the preview after installing packages or making structural changes You can also manually refresh the preview at any time using the **refresh button** in the preview panel. ### Soft Reload A soft reload refreshes the preview without restarting anything. It's a quick way to reconnect and see recent changes. **When to use it:** Sometimes the agent disconnects from the preview and you can't see the latest changes. A soft reload reconnects it and brings everything up to date. **How to soft reload:** * **In the browser preview** — click the refresh button in the preview panel. * **In Expo Go** — hold three fingers on the screen to open the reload menu. * **Ask the agent** — tell the design or software agent to soft reload. For example: > "Soft reload the preview" ### Hard Reload A hard reload fully restarts the development server. It clears cached data and gives your project a fresh start. **When to use it:** If something isn't working and you can't figure out why — the page looks stuck, a change isn't showing up, or the app is behaving strangely — a hard reload often fixes it. These are usually cache-related problems that go away with a restart. **How to hard reload:** Ask the agent to hard reload for you. For example: > "Hard reload" If you've been trying to fix an issue and nothing seems to work, try a hard reload before spending more time debugging. It clears out cached data and restarts fresh — many mysterious problems turn out to be a simple cache issue. ### Runtime Errors If your app encounters a runtime error during preview, CatDoes captures it and makes it available to the agent. The agent can inspect these errors and attempt to fix them automatically as part of its workflow. For more on how the agent monitors and responds to errors, see [CatDoes Watch](/features/watch). ## Mobile Preview with Expo Go Beyond the browser preview, you can test your app on a physical mobile device using [Expo Go](https://expo.dev/go). 1. Download **Expo Go** on your iOS or Android device. 2. Use the **Scan QR Code** option in the preview panel to get a QR code for your project. 3. Scan the QR code with your device to open the app in Expo Go. This lets you test touch interactions, native features, and real-world performance directly on your phone. The browser preview renders your app in a web view, which may look or behave slightly differently from the native mobile experience. Use the Expo Go preview on a physical device to verify native-specific behavior. Use the QR code to share your in-progress app with teammates or stakeholders for quick feedback — no install required, just the Expo Go app. # Lovable to Native App Source: https://docs.catdoes.com/features/lovable Convert your Lovable website into a native iOS and Android app. CatDoes can transform your existing Lovable website into a native mobile application. The process extracts your website's design, branding, and content to create a fully native iOS and Android app.