> ## Documentation Index
> Fetch the complete documentation index at: https://docs.base44.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuring your system prompt

> Set your agent's brand, behavior, and design guidance across your white label workspace.

The system prompt defines how your app-building agent behaves across your workspace. Keep the default prompt when you need Base44 capabilities and extend the agent with [skills and MCP](/developers/white-label/skills-and-mcp). Supply your own prompt when your platform doesn't need those capabilities and you want to define the agent's behavior yourself.

<Warning>
  White label is in [beta](/developers/white-label/overview) and needs to be enabled for your workspace. You need a workspace owner or admin role to change these settings. If you don't see **White label** in workspace settings, contact your onboarding contact.
</Warning>

## Set your brand and agent names

**Custom system prompt** is off by default. When it's off, the page shows only this switch. Turn it on to reveal **Brand**, **Default design system**, and **Agent prompt**.

**To turn on white labeling:**

1. Open your workspace settings in Base44.
2. Under **White label**, click **System Prompt**.
3. Turn on **Custom system prompt**. The switch saves immediately and uses your workspace name as the initial brand name.
4. In the **Brand** card, review **Brand name**. Replace it with the name you want the agent to use for your platform.
5. Optionally, enter an **Agent name**. Leave it empty for the agent to use your brand name.
6. If you changed either name, click **Save** in the **Brand** card.

Both names support up to 48 characters. Use your own names rather than **Base44**. A brand name is required while **Custom system prompt** is on.

To change either name later, edit it and click **Save** in the **Brand** card. **Cancel** discards unsaved name changes.

## Choose how to guide the agent

With **Custom system prompt** on, the **Agent prompt** field determines which approach you use.

| Agent prompt    | When to use it                                                                                                                              | What the agent works from                                                                                                                                                                                                    |
| :-------------- | :------------------------------------------------------------------------------------------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Empty           | You need Base44 capabilities. Enrich the agent through the separate [skills and MCP configuration](/developers/white-label/skills-and-mcp). | Your brand and agent names, Base44's core tool and safety rules, and built-in guidance for entity schemas, the entity SDK, and backend functions when the app has access to them. This default applies to standard web apps. |
| Your own prompt | Your platform doesn't need Base44 capabilities and you want to define the agent's behavior yourself.                                        | Your brand and agent names, Base44's core tool and safety rules, your prompt, and optionally your default design system. Your prompt replaces the built-in capability guidance.                                              |

If you need Base44 capabilities, leave **Agent prompt** empty. Use workspace skills to teach the agent your conventions and MCP connections to give it access to your platform's tools and data. These are configured separately from **System Prompt**.

<Note>
  A prompt changes the agent's instructions, not its permissions. Base44's tool and safety rules still apply, and your prompt can't grant access to unavailable tools or capabilities.
</Note>

## Write and save your prompt

<Tip>
  Use this option when your platform doesn't need Base44 capabilities. Define workspace-wide behavior in your prompt and put context that changes from app to app in [custom instructions](/developers/white-label/custom-instructions).
</Tip>

**To set your own system prompt:**

1. Open **White label** → **System Prompt** in workspace settings.
2. Make sure **Custom system prompt** is on.
3. In **Agent prompt**, enter your instructions. You can use up to 60,000 characters.
4. Click **Save** in the **Agent prompt** card.

Saved changes apply from the next build turn, including the next turn in an existing conversation. Keep a copy of your previous prompt if you want to restore it later. **Cancel** only discards unsaved edits.

### What to include

Your prompt should explain:

* **Role and tone:** What the agent helps people build and how it communicates.
* **Platform context:** How generated apps fit into your product.
* **Development approach:** Which frameworks, libraries, and conventions to follow within the app's supported environment.
* **Data and integrations:** How to work with your platform's own APIs and data sources.
* **Workflow:** When to ask for clarification, how to verify changes, and what to report after a build.

For a platform that uses its own APIs and data sources instead of Base44 capabilities, adapt this starting point with your platform's name and integration details.

```text theme={null}
You are our platform's app-building assistant. Help people build focused
tools for managing their team's work inside our platform.

Use a clear, friendly tone. Keep explanations concise and describe
changes in terms of what someone can do with the finished app.

Build within the app's existing framework and project structure.
Use the supplied design tokens and design rules consistently.

Use the app-specific custom instructions for integration details.
Use only the documented APIs and data sources supplied for the app.
Ask for missing integration details instead of inventing endpoints.
Keep credentials out of client-side code.

Ask a short clarifying question when a missing requirement changes
what needs to be built. Otherwise, make reasonable choices and proceed.
Verify the main interaction after making changes. Explain what changed
and anything that still needs attention.
```

## Include your default design system

The **Default design system** card adds your workspace default's design tokens and design rules alongside your custom agent prompt. It's off by default and applies only when you've saved a nonempty **Agent prompt**.

<Tip>
  First, create a [design system and set it as the workspace default](/Building-your-app/Design-system#setting-a-default-design-system). Wait for it to finish generating before using it with your prompt.
</Tip>

**To include your design system:**

1. Open **White label** → **System Prompt** in workspace settings.
2. Make sure **Custom system prompt** is on and you've saved your **Agent prompt**.
3. Turn on **Default design system**. The switch saves immediately.

The agent receives design tokens, such as colors, typography, spacing, radii, and shadows, plus design guidelines and component styling rules. The prompt addition doesn't include the design system's full component examples, logo, or brand voice. Describe your agent's voice in **Agent prompt**.

If no default design system is ready, the agent continues without this design guidance. Choosing a default on the **Design system** page and turning on **Default design system** here are separate settings.

## Reset or turn off white labeling

<AccordionGroup>
  <Accordion title="Return to the default white-label prompt">
    With **Custom system prompt** still on, standard web apps return to the default white-label guidance. Your custom prompt and the optional design-system prompt addition no longer apply.

    **To remove your custom prompt:**

    1. Open **White label** → **System Prompt** in workspace settings.
    2. Clear **Agent prompt**.
    3. Click **Save** in the **Agent prompt** card.
  </Accordion>

  <Accordion title="Turn off white labeling">
    Turn off **Custom system prompt** on the **System Prompt** page. The switch saves immediately and hides the **Brand**, **Default design system**, and **Agent prompt** cards. Subsequent turns use Base44's standard builder behavior. Your saved names, agent prompt, and design-system preference are kept for when you turn **Custom system prompt** back on. Unsaved changes to brand and agent names are discarded.
  </Accordion>
</AccordionGroup>

## See also

* [Design system](/developers/white-label/design-system): Configure the visual guidance for your apps
* [Custom instructions](/developers/white-label/custom-instructions): Add context for a specific app
* [Skills and MCP](/developers/white-label/skills-and-mcp): Give the agent reusable guidance and tools