# Make a Task better

When a Task gets something wrong, you say what should change, in plain words. Facet works out the fix, tells you what it costs, and puts it live only when it passes every Expectation. You never edit prompts or training data yourself.

## 1. Ask for a change

On any Task page, choose **Ask for a change** (or press ⌘K, Ctrl+K on Windows) and describe what should be different:

> Tickets about refunds are billing, not account.

Add the inputs it got wrong if you have them. They become examples for the new Expectation, and some are hidden to check the fix.

From your agent, the same step is `file_ask`.

## 2. Read the plan

Facet answers with a plan:

- **The Expectation** your Ask implies, such as "labels refund requests billing", with its examples.
- **How often today's version misses it,** measured on those examples.
- **The quote:** the most the fix can cost. Facet picks the approach: rewriting the Task's Instructions costs cents and takes minutes; building a new version costs more and takes longer. It tries the cheaper one first.

If today's version already passes, Facet says so and suggests closing the Ask.

## 3. Approve

Approve the quote and the fix starts. It never spends more than the quote. If it runs out first, it stops and shows how far it got, with **Raise quote and continue** if a bit more would finish it. Approving from an agent asks you to confirm in your agent's window, since it spends money.

## 4. Watch it run

The fix runs on its own; you can close the tab. Its page shows each step as it happens. **Stop** ends it at any point, and you pay only for what ran.

## 5. Review and merge

When the fix is ready, its page shows every Expectation side by side with the live version: what got better, what got worse, and what stayed the same.

- By default, a fix merges on its own when every Expectation passes.
- With **Approve each merge** on, under the Task's **Settings, Merging**, it waits for a Task owner to choose **Approve and merge**.

Once merged, the fix is the new live version (also called Latest), and every caller using the Task's name gets it on their next call.

## Roll back

If a merged change turns out wrong, open **History** and choose **Roll back** on the version before it. Callers get the earlier version at once. Rolling back can itself be undone.

## Next steps

- [Write good Expectations](/docs/expectations): a sharper Expectation makes a cheaper fix
- [Pricing](/docs/pricing): what fixes cost
- [Concepts](/docs/concepts): Asks, Changes and Versions in one picture