Base44 Lets You Edit In-App Agents on a Branch
Base44Base44 now lets users create, edit and delete in-app agents on a branch, from the AI chat or the Agents page in the app dashboard. Changes stay on the branch until merged, while the app and the branch preview keep running main's agents. This lets teams iterate on agent behavior without touching what live users see.
Key Takeaways
- In-app agents can now be created, edited and deleted on a branch, bringing agent work into the same isolated workflow as pages and design.
- Edits can be made through the AI chat or the Agents page in the app dashboard, which lists the branch's own agents.
- Changes stay on the branch until merged, so experiments never reach live users early.
- The app and the branch preview keep running main's agents until the merge, which keeps production behavior stable.
- If main is protected, its agent editor is view-only, and clicking Add Agent there moves the request to a new branch automatically.
- Merging does not push anything live by itself: users see merged agent changes only after publishing from main.
Agents Join the Branch Workflow
Base44 branches give users a separate line of work that starts from the current state of main, the app's primary version. Each branch has its own chat, live preview, builds and version history, so ideas can be tried without changing main. On November 1, 2026, Base44 extended that model to in-app agents: they can now be created, edited and deleted on a branch.
How Editing Agents on a Branch Works
Users can manage agents on a branch in two ways: by asking the AI chat to make the change, or by opening the Agents page in the app's dashboard. On a branch, the Agents page lists that branch's agents, so the view always reflects the work in progress on that line rather than what is live on main.
Changes stay on the branch until the branch is merged. Until then, the app, including the branch's own preview, keeps running main's agents. That separation means a half-finished prompt change or a new tool configuration cannot affect real users while it is still being tested.
Protected Main
Base44 also handles the case where main is protected. In that situation the agent editor on main is view-only. Clicking Add Agent on main and sending the request moves the work to a new branch automatically, so users are steered into the safe workflow instead of being blocked.
What Stays Shared
Branches in Base44 share some things with main, including live data, integrations, secrets, automations, workflows, settings, domains and the published version. Pages, design, chat and preview are branch-specific. Merging brings branch work into main, and users see it only after publishing from main.
Why It Matters
Agents behave like part of an app's logic, and small prompt changes can alter outcomes. Being able to change them on a branch, review the result and merge deliberately brings agent work in line with how Base44 already treats pages and design.