> 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/3.-understanding-the-workspace-editor.md).

# 3. Understanding the Workspace Editor

<figure><img src="/files/c8csjGLEFAtnI2HPrwlE" alt=""><figcaption></figcaption></figure>

When a prompt is processed, the Buzzy Workspace is populated with structured views of your app. The sidebar navigation is organised into the following sections:

***

## Dashboard

A central overview of your app, showing key information such as app name, creator, creation date, and last modified date. The Dashboard also provides quick links to documentation and getting started guides, as well as a summary of your app's development progress and suggested next steps.

***

## BUILD

#### 🔹 Brief

A high-level summary of what your app does, based on your prompt. You can revise this at any time to re-guide the AI.

#### 🔹 Blueprint

An auto-generated list of screens and key components. This gives a birds-eye view of your app's structure and user flow. Note: Blueprint is hidden for Figma-created apps.

#### 🔹 Design

Where you view and edit the actual screens. This includes layout, components, bindings, actions, and screen-level logic.

Inside the Design workspace you will usually work across four areas:

* the left panel for screen structure and assets
* the centre preview for interacting with the current screen
* the right-hand tabs for **Properties**, **Code**, and **Debug**
* the AI chat panel for prompting, diagnosis, and autofix suggestions

The **Debug** tab is contextual to the current screen or selected node. It shows issue counts, data-binding details, runtime context, and entry points for AI diagnosis. The AI chat panel also includes a dedicated diagnose flow, so you can start debugging from either side of the editor.

For Figma-created apps, screens are previewed here but are not directly editable. A button is provided to open the linked Figma file for editing.

#### 🔹 Data

A list of data collections (e.g. tasks, users, products) and their fields. These power your app's dynamic content.

***

## CONFIGURE

#### 🔹 Constants `Beta`

Secure storage for API keys, passwords, database URLs, and other configuration values used by your app and its Functions. Constants can be regular (plain text) or secret (AES-encrypted). Use the `BUZZYCONSTANTS()` syntax to reference them in your Functions' environment variables.

#### 🔹 MCP `Beta`

Configure [Model Context Protocol (MCP)](/the-building-blocks/mcp.md) for your app. MCP enables AI assistants like ChatGPT and Claude to interact with your app through natural language — querying data, creating records, and performing actions. Buzzy automatically generates the MCP server and tools from your app's data model.

#### 🔹 Functions `Beta`

Build and manage serverless [Buzzy Functions](/the-building-blocks/buzzy-functions-and-constants/buzzy-functions.md) — AWS Lambda functions that extend your app with custom code for external API integrations, AI processing, webhooks, and complex business logic. Functions can be written manually or generated with AI from a natural language prompt.

#### 🔹 People

Where you can manage access and permissions for your app.

#### 🔹 Settings

Control your app's settings and core information here, including privacy and publish status, custom header code and more.

***

## RELEASE

#### 🔹 Publish

Shows your app's publish information (live URL, QR code to preview on a device) and more. It also includes deployment controls and information — you'll need to sign up to a deployment plan to get your app into one of the app stores.

#### 🔹 Tests

Create and run reusable [Release Tests](/getting-started-with-buzzy/new-buzzy-ai-v3/9.-release-tests.md) for important app workflows before you publish. The Tests section includes saved test definitions, manual authoring, viewport targets, and run history.

#### 🔹 Versions

Buzzy includes version control so you can roll back to previous versions if needed.


---

# 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/3.-understanding-the-workspace-editor.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.