Features

Code view

In the Code tab, you can manage your app code and tweak it without prompting. Having said that, we do recommend to be careful when changing the code directly since such actions are not tracked in the release history. It will be impossible to revert to a specific checkpoint if something goes wrong.

You can right click on any folder or file to rename or delete it, and you can also add new files or folders to the existing structure. The Search bar at the top allows you to quickly search for any file you want to update.

Below all the folders, there's an AGENTS.md file—here you can add specific app-level instructions that the Agent will refer to when building an app. For example, you can give more details about your application context, specify your coding style or design guidelines, or just any other things you want the agent to apply consistently while building.

It always helps to be specific and clear in your instructions and provide examples to help the Agent better understand your preferences.

Migrations & Screenshot settings

For each app you build, you can access its settings—either from the UI Bakery icon in the Builder or from the Workspace menu—and, among other settings, configure the migrations and screenshot tools.

With migrations, you can either choose to apply them automatically or manually. If you choose manually, then each time there's a migration, a prompt will appear in the chat and you can select Apply or Reject there.

By default, the Always allow option is enabled for all new projects.

The same with screenshots—you can either choose the automatic or manual option. If you choose Always ask, then each time the agent needs to take a screenshot to investigate some UI issues, for example, you'll see a prompt with the following options: Always allow, Allow once, and Deny once.

You can select the option that best fits your specific needs.

Both migrations and screenshot settings are NOT global and can be configured for each app separately.

Multi-page apps

With the UI Bakery AI agent, you can create multi-page applications that support persistent state and URLs with query parameters.

In the URL, you can see the page you're currently on—the parameter changes when switching between pages. The app also stays on the same page after reload and works with browser back/forward navigation as well.

Actions

In your app, it's possible to create conditional actions so that you can control action execution. It can be especially useful in such cases as:

• Not loading data until all filters have been selected

• Fetching data only after a modal or tab is opened

• Blocking mutations if a form is invalid or permissions are missing

• and others

User context

The AI agent can access information about the currently logged-in user through the {{user}} context. This allows you to personalize actions, filter data, or apply user-based permissions.

Common fields include:

• {{user.email}}

• {{user.name}}

• {{user.id}}

Login

If you want to add login to your app, the AI agent will suggest the following options:

• Built-in UI Bakery auth - Users can access the app through the UI Bakery workspace login. This option is good for internal apps and you can use SSO, RBAC, audit logs, and other out-of-the-box security features.

• Custom auth - Allows you to create your own custom login page with custom user database and auth logic within the application. This is a good choice for customer portals and similar apps where users are relevant only for this specific application.

You can choose one of these options in the prompt and the AI agent will implement the authentication.