> For the complete documentation index, see [llms.txt](https://docs.buzzy.buzz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buzzy.buzz/getting-started-with-buzzy/new-buzzy-ai-v3/4.-editing-your-app-via-ai.md).

# 4. Editing your app via AI

Once your app has been generated, you can continue to use AI to make changes at any time. Open the **AI** chat panel (top right in the toolbar) and describe what you want to change in plain language.

AI editing works across several areas of your app:

* **Theming** — Ask AI to change your app's look and feel. You can switch between built-in themes (e.g. *"Switch to the Zen theme"*), toggle dark or light mode, adjust colours, typography, shadows, borders and more. See the [Working with themes](/getting-started-with-buzzy/new-buzzy-ai-v3/7.-working-with-themes.md) section for details.
* **Data model** — Ask AI to add, rename or restructure data collections and fields (e.g. *"Add a priority field to the Tasks table"*, *"Create a new Comments collection linked to Posts"*).
* **Screens & layout** — Request new screens, rearrange layouts, or add UI components (e.g. *"Add a dashboard screen with summary cards"*, *"Change the list to a two-column grid"*).
* **Logic & actions** — Describe behaviour changes such as navigation flows, form submissions or button actions (e.g. *"When the user submits the form, navigate to the confirmation screen"*).

> 💡 Tip: You can combine multiple requests in a single prompt — for example *"Add a search bar to the top of the Products screen and switch to dark mode."*

## Diagnosing before changing

When something looks broken, it is often better to diagnose first and edit second.

Buzzy's AI panel supports both workflows:

* normal editing prompts, where you ask Buzzy to change the app
* debug diagnosis, where you ask Buzzy to explain what is wrong before you change anything

### Using the debug button

If you already have the relevant screen or component selected, click the debug or diagnose entry point in the AI panel without adding extra text. Buzzy uses the current editor context to inspect the selected node or screen and returns a structured diagnosis.

### Guiding the diagnosis with a short prompt

You can also add a short prompt before diagnosing, especially when you want Buzzy to focus on a specific symptom. For example:

* "Why is this list empty?"
* "Check whether this button is navigating to the wrong place."
* "Find out why this form does not save."

Keep the prompt short. The editor context already carries most of the technical detail.

### From diagnosis to autofix

Diagnosis results can include one or more recommended fixes and an autofix button. Review the diagnosis before you apply a fix. If you want a deeper view of the current binding or issue counts first, open the **Debug** tab in the right-hand panel and launch diagnosis from there instead.

For the full workflow, see [Debugging with the Debug Tab and Debug Agent](/getting-started-with-buzzy/new-buzzy-ai-v3/6.-debugging-with-the-debug-tab-and-agent.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.buzzy.buzz/getting-started-with-buzzy/new-buzzy-ai-v3/4.-editing-your-app-via-ai.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.