Skip to main content
Use the AI chat to make changes to your connected repository and test them in a development preview. When the AI finishes each reply, Base Code commits and pushes its changes to your working branch on GitHub. You make these changes on your branch in the Base Code editor, the workspace where you chat with the AI, check the preview, and browse your code. Open your branch from the Base Code sidebar to get there.
If a push to GitHub fails:You see a banner in the AI chat, and Base Code backs up the AI’s work on a separate branch. This happens when your branch has new commits on GitHub that conflict with the AI’s changes, or when the branch was deleted on GitHub. In the banner, click:
  • Fix it: The AI merges GitHub’s changes or recreates the branch, then pushes.
  • Continue on a new branch: You keep building from the backup.

Choosing the AI model

Base Code uses Auto by default to choose an AI model for each request. You can pick a model yourself when you want more control.
You need a Builder plan or higher to choose a model yourself.
To choose an AI model:
  1. Open your branch in Base Code.
  2. Click the model at the bottom of the AI chat.
  3. Select the model you want to work with.
When you choose a model yourself, you can also set its effort level from Effort in the model picker. This works in the prompt box on the Base Code start screen too, and the level you pick applies to the task you start.

Adding Google Drive files

Give the AI chat a brief, spec, or design from your Google Drive when you start a branch from the Base Code start screen. You can also add files the same way in the prompt box on your branch. To start a branch from a Google Drive file:
  1. Go to Base Code to open the start screen.
  2. Click the Add icon in the prompt box.
  3. Click Upload from Google Drive.
  4. If prompted, click Connect Google Drive, then allow access in Google.
  5. Select one or more files from My Drive or a shared drive. You can choose:
    • Google Docs, Sheets, and Slides
    • Word, Excel, and PowerPoint files
    • PDFs and images
    • Text, CSV, HTML, XML, and JSON files
  6. (Optional) Describe the change you want to make in the prompt box.
  7. Click Create branch.

Stopping the AI

Stop the AI chat while it’s working, then send a new message to change direction. Changes already committed to your branch stay, and edits the AI hasn’t committed yet are discarded. To stop the AI:
  1. Click the Stop generating icon in the prompt box while the AI chat is working on your branch.
  2. (Optional) Send a new message with what you want instead.
If you stop branch creation from the start screen, Base Code puts your prompt back in the prompt box and removes the new branch from Base Code.

Expanding the chat

Hide the preview so the AI chat fills the editor, then bring the preview back when you want to check your work. The chat returns to its regular width when you switch between Preview, Dashboard, and Code, or open a different file.
Expanding the chat is available on desktop.
To expand or shrink the chat:
  1. Open your branch in Base Code.
  2. Click the Expand chat icon in the toolbar above the AI chat.
  3. Click the Shrink chat icon to show the preview again.
The AI chat filling the Base Code editor with the preview hidden and Shrink chat outlined

The expanded AI chat


Previewing monorepo apps

When your repository has several apps, such as a website and an API, each running app gets its own tab above the preview. You can choose which apps run on each branch, and show 2 of them side by side.

Choosing apps to run

Run only the apps you’re working on. To choose the apps that run on a branch:
  1. Open your branch in Base Code.
  2. Click the Apps icon in the toolbar above the preview, or click Add app at the end of the tab row.
  3. Select each app you want running in Apps to run on this branch.
    Base Code also selects any apps your chosen apps depend on. At least one app keeps running, and on main the main project always runs.
  4. Click Done.
When you create a branch, you can also choose its apps from Run in the prompt box.

Using split view

Show 2 apps side by side, for example to check your website against your API.
Split view is available on desktop.
To show 2 apps side by side:
  1. Open your branch in Base Code.
  2. Click Split view at the end of the tab row.
  3. Click Show or Start next to the app for the empty side.
Working with split view:
  • Hover over the joined tab to Swap sides or to split it back into 2 tabs.
  • Click Exit split view to go back to one app per tab.

Reviewing your changes

Check exactly what changed before you ask anyone to review it. To review your changes:
  1. Open your branch in Base Code.
  2. Open the changes you want to check:
    • One reply’s changes: Use the file list below that reply in the AI chat.
    • Every change on the branch: Click Create PR in the editor, or click the PR number if one already exists. This shows the changes and doesn’t open a pull request yet.
  3. Click a file name to see its diff, with the lines added and removed.

Reverting a file

Undo the changes you don’t want in a file, with the revert saved as a new commit on your branch.
Reverting a file undoes all its committed changes on the branch, not just the changes from one reply.
To revert a file:
  1. Open your branch in Base Code.
  2. Find the file below the AI chat reply, or in the branch’s file list from Create PR or its PR number.
  3. Click the file to expand it, then click Revert file.
  4. Check that the right file appears in Revert branch changes?, then click Revert.
Reverting several files at once:
  • Below a reply: Click Revert all and confirm to revert every file that reply changed.
  • In Create pull request: Click Revert all and confirm to revert every file on the branch.

Using repository skills

Teach the AI chat your team’s workflows with skills stored in your repository. The AI chat reads a skill when it fits your request. Each skill has a name, a description, and instructions, and applies to everyone working on the project, on every branch. Base Code finds skills in these places, at the root of your repository or in a subfolder:
  • Skill folders: A SKILL.md file in a folder under .agents/skills, .claude/skills, or .codex/skills.
  • Claude Code commands: Markdown files in .claude/commands.
  • Local plugins: Skills from Claude Code or Codex plugins stored in your repository.
Only the app owner can turn repository skills on or off.
To manage repository skills:
  1. Open your branch in Base Code.
  2. Click Dashboard in the editor.
  3. Click Repository skills.
  4. Choose what you want to do:
    • Read a skill: Click the skill to see its instructions.
    • Turn a skill on or off: Click the switch next to the skill. Skills are on by default.
    • Show a new skill: After you add a SKILL.md file to your repository, click Refresh.
Using skills in the AI chat:
  • Use a skill right away: Type / in the AI chat, then select the skill.
  • Workspace and personal skills: The AI chat uses these too. When one shares a name with a repository skill, the AI chat uses the repository skill, unless you pick a skill in the chat.

Adding secrets

Give your project the API keys and other credentials it needs without putting them in your repository. The AI chat asks you for a secret when your project needs one.
How secrets work:
  • Shared and kept: Secrets are encrypted, shared across branches, and kept when your environment rebuilds.
  • Updates: Changes and removals apply right away to running branches. Inactive branches pick them up when you next open them.
To add a secret:
  1. Open your branch in Base Code.
  2. Click Dashboard in the editor.
  3. Click Secrets.
  4. Click Add Secret.
  5. Enter the Secret Name and Secret Value, then click Add Secret.
Adding secrets in bulk: Click Import .env, then upload or paste your file. Each KEY=VALUE line becomes a secret. An existing secret with the same name is overwritten.

Viewing infrastructure

See what your project runs on, such as a web app, an API, a database, or a cache. Base44 finds these services in your code and runs private copies of them for your preview, so your real databases and services stay as they are. Each app shows whether it’s running on the current branch, and each service, such as a database, shows its status and where Base44 found it in your code. To view your project’s infrastructure:
  1. Open your branch in Base Code.
  2. Click Dashboard in the editor.
  3. Click Infrastructure.
    If you see Your app’s workspace is asleep, your project’s preview environment is paused. Send a message in the AI chat or open the preview to wake it, then refresh.
  4. (Optional) Choose what you want to do:
    • Preview an app: Click Preview next to the app.
    • Start or stop an app on this branch: Click Start or Stop next to the app.
    • See the latest status: Click the Refresh icon.

Using Verify as you

When you sign in to your app inside the preview, the AI can reuse that session to check screens that need a signed-in user. Your session isn’t shared with other collaborators. Verify as you is on by default, and the setting applies to everyone working on the app. To turn Verify as you on or off:
  1. Open your branch in Base Code.
  2. Click Dashboard in the editor.
  3. Click Infrastructure.
  4. Turn the switch next to Verify as you on or off.
    When you turn Verify as you off:
    • Other collaborators: Their saved sessions are deleted.
    • Your session: It stays until 24 hours after it was last used, in the preview or by the AI. To end it sooner, sign out of your app in the preview.