Orbit Agent changes your app from a plain-language request. You describe the change, then inspect the app to check the result.

## Requests change the app, not a separate copy

You can edit an app yourself or ask Orbit to make the edit. The [Orbit product overview](https://orbitapps.io/) describes both paths.

A request should name the part of the app to change and the parts to keep. A page change and a data change need different checks.

For example, a request to add a field does not prove that a page displays that field. A page that displays a field does not prove that the live app stores its value.

## Where you enter a request

In the app editor, the agent input sits at the bottom of the canvas. Its collapsed label is **Ask Orbit...**.

Select the input to open the text box. The placeholder reads **Describe what you want to build...**. Its accessible name is **Composer prompt**.

The arrow button at the bottom right submits the request. The button has no visible text label. Its accessible name is **Send**.

## A request with a clear boundary

The following example adds an optional field to an existing `requests` table. The table and field names are examples:

> Add an optional text field named delivery_notes to the requests table. Keep all existing fields and records. Leave delivery_notes empty for existing records. Do not change the pages yet.

This request names the field, its type, its empty-value rule, and what must stay unchanged. Follow [Add a field](/guides/add-a-field) for the full task and its checks.

## Check the app, not just the reply

Use **Data Model** to inspect a requested table or field. Use **Mockup** to inspect a requested page change.

For the example above, check that `delivery_notes` appears in `requests` and that the existing fields remain. Confirm the field's type and empty-value rule before you use it.

A model check does not replace a test with saved data. Before launch, [test the app's main task and access rules](/guides/review-an-app-before-launch).

If the result differs from your request, name the exact difference in your next request. Keep the correction limited to that difference.

## What a request does not establish

A request is not proof that the change works for every user or that a live deployment contains the change. Check the relevant page, data, and access rules separately.

Orbit composes existing UI elements, integrations, and a database. The product does not provide a code-file escape hatch. See [what Orbit is](/get-started/what-orbit-is) before you choose it for a project that needs custom code files.