> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/ai-app-builder/refine-an-app/request-focused-changes.md).

# Request focused changes

Describe one observable change, identify its target, and say what should stay the same.

## Request a revision

1. Return to the chat for the task.
2. Name the page and component or action.
3. State the expected behavior using actual field names.
4. Send the request and wait for it to finish.
5. Test the changed behavior and a nearby behavior that should be unchanged.

> On the Tickets page, add a Status filter above the table. Keep the existing columns and sort order. Choosing Open should show only records where Status is Open.

Other examples:

* “In the ticket detail view, show Assigned to below Priority.”
* “Require a rejection reason on the approval form. Keep the existing approval permissions.”
* “On mobile, keep the New ticket button visible without horizontal scrolling.”

For a visual target, [select the component in Preview](/ai-app-builder/refine-an-app/edit-components-in-preview.md) and enter the change there.

## If the revision is too broad

Identify the unintended change and request a correction to that specific behavior. Compare the result with your last working checks before continuing.

Use [Console and logs](/ai-app-builder/preview-and-troubleshoot/inspect-app-console-and-logs.md) for an error and [the review checklist](/ai-app-builder/refine-an-app/review-and-refine.md) for behavior that looks plausible but is wrong.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/ai-app-builder/refine-an-app/request-focused-changes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.