> 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/app-builder/app-workspace.md).

# App Workspace

The app workspace is where you build, inspect, test, and share an app. Describe a change, review the live preview, then move through the App Builder workflow.

<figure><img src="/files/E4D1ZOYIIEc8XGFKs98w" alt="The app workspace, with the build conversation, live preview, and workspace panels"><figcaption><p>The app workspace.</p></figcaption></figure>

<table data-view="cards"><thead><tr><th>Next step</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td>Set up data, domains, and integrations</td><td><a href="/pages/6de8c0921a81fc6dc038359c161a4825e5e9aa3e">/pages/6de8c0921a81fc6dc038359c161a4825e5e9aa3e</a></td></tr><tr><td>Validate the app before release</td><td><a href="/pages/c10eed6161aadb656ac4137fce98a06ced6ec452">/pages/c10eed6161aadb656ac4137fce98a06ced6ec452</a></td></tr><tr><td>Publish the current version</td><td><a href="/pages/KDQL1trGEyacZ7JGRO4O">/pages/KDQL1trGEyacZ7JGRO4O</a></td></tr></tbody></table>

### Describe and build

Use the conversation to describe the change you want. Qore plans the work, waits for your approval, builds the app, and confirms when **Live preview is ready**.

<figure><img src="/files/5VvtiZCU4gn94ptlkwoV" alt="The build conversation, describing a change and showing the plan/approve/build flow"><figcaption><p>Describing a change in the build conversation.</p></figcaption></figure>

Each turn shows its work time and token usage. Open the token total for model-level input and output usage.

<figure><img src="/files/nzDySU1ar83KsUkHaojQ" alt="The token usage breakdown for a build turn, showing model-level input and output usage"><figcaption><p>Model-level token usage for a build turn.</p></figcaption></figure>

#### Fix errors

Forward a preview error to the build agent. The request includes the error type and message. Qore fixes the app and rebuilds the preview.

{% hint style="info" %}
Fixing an error is another conversation turn. Describe or forward the error, then review the rebuilt preview.
{% endhint %}

{% hint style="info" %}
**Fix with AI** sends the reported issue to Qore's build agent. Review the rebuilt preview before you continue.
{% endhint %}

### Continue building

Choose a suggested next step, or enter another request. **Upgrade your app** can add a database for persistent data or an AI agent for app intelligence.

{% hint style="info" %}
Each round follows the same flow: plan, approve, and build. Nothing is built before you approve the plan.
{% endhint %}

### Preview

Use the live preview after every change. Switch between desktop, tablet, and mobile widths to check responsiveness. Each preview includes a **Built with QORE** badge.

<figure><img src="/files/MlHqg16qkvcraiwMiLYr" alt="The live app preview, with desktop, tablet, and mobile width controls"><figcaption><p>The live preview.</p></figcaption></figure>

### Explore the workspace

Switch the centre panel between **Preview**, **Code**, and **Agents**.

#### Code

* Inspect the generated source in the file tree. It includes the frontend, tests, project configuration, `app.run.json`, and `APPLICATION_PLAN.md`.
* Select a file to read it, edit it, download it, or connect its repository to GitHub.
* Use the build conversation for most app changes.
* For repository workflows, see [Code Access & Git Integration](/sdks-and-code-access/code-access-and-git-integration.md).

<figure><img src="/files/wXzBF0Ehx5inoYyPqDWD" alt="The Code panel, showing the generated file tree and an open source file"><figcaption><p>Inspecting and editing generated source in the Code panel.</p></figcaption></figure>

#### Agents

* Use **Agents** to add automation, data processing, and logic.
* Select **Build an Agent** for a new agent, or **Attach Agents** for an existing one.
* For attachment steps, see [Integrate an agent](/workflow-guides/integrate-an-agent.md).

<figure><img src="/files/KcK3luHXYSCJ4YDKbvXr" alt="The Attach Agents dialog, listing existing agents to attach to the app"><figcaption><p>Attaching an existing agent to the app.</p></figcaption></figure>

### Credits

The Credits meter shows what this app has consumed—the Credits used, the Cost, and when the figure was last synced. Building an app spends credits, so keep an eye on it as you iterate. For account-wide usage and limits, see [Billing](/governance/billing.md).

<figure><img src="/files/eF151T4y13E8y7VLS1eA" alt="The Credits meter, showing credits used, cost, and last synced time"><figcaption><p>The Credits meter.</p></figcaption></figure>

### Versions and publishing

The version selector lists builds newest first. **Latest** marks the newest build. **Published** marks the version users see. *Uncommitted changes* marks work outside a version.

<figure><img src="/files/fAUSnOFgcDzCAKAmmkpc" alt="The version selector, listing builds newest first with Latest and Published markers"><figcaption><p>The version selector.</p></figcaption></figure>

Select a version to review or return to it. To make one live, follow [Deploy an app](/app-builder/deploy.md).

### Share

Select **Share**, beside the version selector, to share the app.

### More

The **More** menu reflects the selected build version. Use it to inspect:

* [Analytics](/app-builder/analytics.md) for published-app engagement
* [DB Explorer](/app-builder/build/db-explorer.md) and [Data Flow](/app-builder/build/data-flow.md) for app data and architecture
* [Testing](/app-builder/testing.md) and [Security Scans](/app-builder/security-scans.md) before release


---

# 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/app-builder/app-workspace.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.