> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/workflow-guides/plan-vs-build-mode.md).

# Plan vs Build Mode

The workspace prompt box has two modes:

* **Build Mode** generates your app.
* **Plan Mode** lets you discuss its logic first.

This guide shows when to use each mode and how to switch.

## Prerequisites

{% hint style="info" %}
You need access to a Qore workspace. Open the Dashboard or App Builder.
{% endhint %}

## Mode overview

The mode control sits **inside the prompt box**, at the bottom-right, labeled **Build** with a ⚡ icon and a chevron.

<figure><img src="/files/iECWDgGxEEBQRj1qIIaU" alt=""><figcaption><p>The mode control (⚡ Build ⌄) sits at the bottom-right of the prompt box</p></figcaption></figure>

{% hint style="info" %}
You never have to turn Build Mode on — it is the default. Plan Mode is the mode you *opt into* when you want to align before building.
{% endhint %}

The two options, as shown in the dropdown:

* **Build Mode** — Turn your idea into an app. AI plans, builds, and iterates as you refine it.
* **Plan Mode** — Discuss ideas and define the app before starting the build.

## When to use which

Use **Plan Mode** when you want to map a workflow (loan eligibility, KYC), review the approach, or align with stakeholders *before* code is written.

Use **Build Mode** when you want to generate a working app from a prompt and iterate on it live.

## Steps: switching modes

{% stepper %}
{% step %}

### Open the mode control

In the prompt box, click the **⚡ Build ⌄** control at the bottom-right. A menu opens with **Build Mode** and **Plan Mode**.
{% endstep %}

{% step %}

### Select Plan Mode

Choose **Plan Mode**, then send a prompt. The workspace returns a plan to review and refine instead of building.

<figure><img src="/files/wrDyfB0shdUFAUYieLv3" alt=""><figcaption><p>The mode dropdown, showing Build Mode and Plan Mode</p></figcaption></figure>
{% endstep %}

{% step %}

### Switch back to Build Mode to execute

When the plan looks right, reopen the control and select **Build Mode**, then prompt to build.
{% endstep %}
{% endstepper %}

## Verify

In **Plan Mode**, prompts return a reviewable plan (no code runs).

In **Build Mode**, prompts start building.

## Common issues

* **My prompt built the app when I only wanted to plan.** You were in Build Mode — switch to Plan Mode before prompting.
* **I selected Plan Mode but nothing is building.** That's expected; switch back to Build Mode to generate.
* **I can't find a mode toggle in the header.** The control is inside the prompt box (bottom-right), not the top header.

## Other prompt box controls

{% hint style="info" %}
The prompt box includes these additional controls:

* **+ menu** — attach files or import an app package.
* **Branding, target, and model controls** — configure the app before building.
* **App** and **Agent** tabs — choose what you create.
  {% endhint %}

## Related pages

Read [Get Started](broken://spaces/0qmgQjJ5aArDTj2ACFHG/pages/QsxktQ2po9Whjaaa5slS) for first-time setup.

Read [Build](/app-builder/build.md) for app-generation details.

Next step, [create an app](/workflow-guides/create-an-app.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.uptiq.ai/workflow-guides/plan-vs-build-mode.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.