AI modes

Pick a mode to tell WeWeb AI what you want to do. Each mode focuses the AI on a specific task so you get clearer, more accurate results.

Quick reference

Mode	Best for	Availability
Build	creating or updating your app	always
Plan	reviewing a build plan before anything is created	always
Ask	questions about WeWeb and your selected context	always
Edit workflow	updating the workflow that is open	when a workflow is open
Edit component	updating a custom coded component	when a coded component is in context
Edit formula	editing formulas	coming soon

The mode selector

Open the Select AI mode menu in the chat input area. Available modes change based on what you're doing.

TIP

Modes that target a single item are disabled until you have the right context. For example, Edit workflow becomes available when a workflow is open, and Edit component becomes available when you add a coded component to context.

WeWeb AI can also switch modes for you. When you open a workflow, it selects Edit workflow. When you add a coded component to context (without selecting an instance on the page), it selects Edit component.

Build

Build is the default mode for making changes to your app. Use it to design layouts, style elements, connect data, create workflows and formulas, work with your backend, and generate new custom coded components.

Try:

"Create a product card with image, title, price, and an add-to-cart button"

"Create a products table with name, price, and description"

"On submission of this form, I want to use my registration workflow"

Plan

Plan lets WeWeb AI explore your project and draft a detailed build plan before making changes. Nothing is created until you approve the plan.

Use Plan when you want to review scope, technical details, and the assets WeWeb AI intends to create or update (tables, pages, workflows, components, and more) before anything is built.

1. Select Plan and describe what you want.
2. When the plan is ready, click Review the plan on the plan card in the chat.
3. In the Build plan panel, review the Summary, Technical details, and Assets created / updated sections.
4. Choose one of:
   • Approve & build: Switches to Build mode and executes the plan
   • Ask for changes: Keeps you in Plan mode so you can refine the plan in chat

Try:

"Plan a task management app with a dashboard, task list, and user authentication"

TIP

Plan mode supports the same file attachments as Build (images, PDFs, and text files).

Ask

Ask answers questions about WeWeb and about the context you provide. Use it when you need clarity before changing anything, or to troubleshoot and learn best practices. Ask is read-only, so it will not apply changes to your app.

Try:

"How does this workflow handle authentication?" "Explain how table views are used on this page"

TIP

Ask works best with context. Pass the page, element, workflow, or formula you care about to get tailored explanations.

Edit workflow

Edit workflow updates the workflow that's currently open. Use it to add actions, conditions, error handling, or connect an existing workflow to new logic. Open the workflow editor first.

This mode does not support file attachments.

Try:

"Add error handling if this workflow fails" "I want to show a confirmation popup at the end of the workflow"

Edit component

Edit component updates a custom coded component that's in your AI context. Use it to add properties, change behavior, or refine styling on an existing component.

To use this mode, use Edit with AI from Add Element → Coded components, from the component code editor, or from a coded component artifact in chat. That adds the component to AI context and switches to Edit component.

If you only select an instance on the page, WeWeb AI stays in Build so it can update that element's properties and styling.

Try:

"Add a loading state property to this component" "Change the default color to match my design system"

Edit formula

Edit formula is shown in the mode selector, but it is not available yet. For now, use Ask to understand a formula, or Build when you want AI to help plan related changes.

Try:

"How can I update this formula to handle empty values?"

Effort level

In Build mode, a button next to the mode selector shows how much effort WeWeb AI puts into your request. Effort is the time the AI spends thinking before it starts working: less effort means a quicker answer, more effort means it reasons longer and makes fewer mistakes.

Click the button to open the slider, which runs from Faster on the left to Smarter on the right, and pick one of three levels:

• Fast: Quickest answers, best for small tweaks
• Balanced: A good speed and quality trade-off for specific tasks
• Max: The AI thinks longer and makes fewer mistakes, recommended for complex features or debugging

If you never change it, WeWeb AI runs on Max. Your choice is saved with the project, so it applies to your next prompts and to everyone else working on the same project.

EFFORT AND TOKENS

Faster levels use fewer AI tokens, smarter levels use more. If you are working through a series of small changes, Fast or Balanced will stretch your allowance further.

The effort button is only available in Build mode.

AI token usage

Every prompt you send uses AI tokens, the unit WeWeb counts AI work in. The round gauge in the chat input area fills up as you use your allowance, so you can keep an eye on it without leaving the editor.

Click the gauge to open the AI tokens panel:

• Resets on Is the date your allowance renews
• You Is what you have used against your own limit
• Workspace Is what everyone in your workspace has used, shown when the workspace has its own limit
• Manage plan Opens your workspace plans page in a new tab

The gauge updates after each response, and changes color as you get close to your limit so you notice before you run out.

WARNING

Once the allowance is used up, WeWeb AI stops answering until it resets or you update your plan. Both your own limit and your workspace limit can block a request, which is why the gauge shows whichever one is closest to being reached.

Tips for choosing a mode

• Start with Build for most app changes, including backend tables and APIs
• Use Plan when you want to review scope and assets before anything is built
• Switch to Ask when you need clarity first
• Use Edit workflow when you have a workflow open and want AI to update it
• Use Edit component when you want to change the code of an existing custom component
• Use Ask for read-only explanations before asking Build to make changes

Examples

Plan a larger feature

1. Plan: "Plan a customer portal with login, dashboard, and support tickets"
2. Review the build plan and click Review the plan, then Approve & build
3. Build: "Adjust the dashboard layout to match my brand colors"

Build a new feature

1. Ask: "What's the best way to implement favorites?"
2. Build: "Add a heart icon that toggles favorites"
3. Build: "Create a user_favorites table"

Debug a problem

1. Ask: "Why doesn't this button trigger the workflow?"
2. Build: "Fix the click event so it runs the workflow"

Create custom functionality

1. Ask: "Do we have a native image cropper?"
2. Build: "Create an image cropper with drag handles"
3. Build: "Add it to the profile page"
4. Edit component: "Add a reset button that clears the crop selection"