# AI assist

> The assistant in the output pane - what each action does, exactly what it costs, which ones are free each day, and when you are not charged at all.

Source: https://www.revquix.com/docs/projects/ai-assist
Last verified: 2026-09-03

---

The assistant reads your project and answers about _your_ code. It is in the output pane, next to
the run results.

## The actions and what they cost

| Action               | Credits | Free per day | Changes your code |
| -------------------- | ------- | ------------ | ----------------- |
| Explain error        | 1       | 3            | Suggests a patch  |
| Explain code         | 1       | 2            | No                |
| Explain a failed run | 1       | 1            | No                |
| Add comments         | 1       | -            | Suggests a patch  |
| Fix error            | 2       | -            | Suggests a patch  |
| Optimise             | 2       | -            | Suggests a patch  |
| Generate tests       | 2       | -            | Suggests a patch  |
| Review               | 2       | -            | No                |
| Write a README       | 2       | -            | Suggests a patch  |
| Explain the project  | 4       | -            | No                |

**Large inputs cost more.** An extra credit is added for roughly every 12,000 characters sent. A
single file is normally one unit; asking about a whole large project is not.

> **Note** - You are quoted before you are charged
>
> The panel tells you the cost before you confirm, and that quote already accounts for your free
> allowance and for the cache below. It is a real quote, not an estimate.

## When it is free

- **Your daily free runs** on the three explain actions, as listed above.
- **A repeat of something you already asked.** Same code, same action, same day - the answer is
  replayed from cache and costs nothing.

⚠ A cache replay does **not** consume one of your free daily runs either. Asking the same question
twice is free the second time in both senses.

## Patches

Some actions propose a change rather than describing one. You get a diff - the current code beside
the suggestion - and you choose.

> **Warning** - Rejecting a patch does not refund the credit
>
> You paid for the answer, and you got one. Refunding on reject would make "generate, reject, repeat"
> a free generation loop, and would quietly reward rejecting good output. Read the quote before you
> confirm rather than treating reject as an undo.

Accepting applies the change to your file, where the editor's normal undo works on it.

## What it can see

Your project's files. It does not have your run output unless you use the action that is about a
failed run, and it does not know anything about your account beyond the code in front of it.

## Getting better answers

- **Ask about a specific file** rather than the whole project when you can - cheaper and sharper.
- **Use "Explain a failed run" for a failure**, not "Explain code". It is the one that gets the
  error.
- **Say what you expected.** "This should print 12 and prints 0" beats "why is this broken".

- [Tests](https://www.revquix.com/docs/projects/tests) - Checking behaviour rather than reading it.

- [Credits](https://www.revquix.com/docs/payments/credits) - Where credits come from.