AI Checklists
For long multi-step tasks, Revix builds a visible checklist that updates as it works. You see each item's status change in real time — so you can follow along, jump in early, or redirect the AI before it goes too far down a wrong path.
What checklists are for
When you ask for something with many steps — "build me a working shop system" or "refactor this combat module" — the AI uses the checklist tool to plan upfront. It writes out the steps it intends to take, then ticks them off as it completes them.
This gives you three things:
- A plan you can audit before work starts. If the AI is heading in the wrong direction, you spot it immediately.
- Live progress visibility. You see what's done, what's running, and what's still queued.
- A natural place to interrupt. You can stop the AI between items rather than mid-edit.
Item statuses
Each checklist item carries one of three statuses:
| Status | Meaning |
|---|---|
| `pending` | Not started yet — queued for later in the run |
| `in-progress` | The AI is actively working on this item right now |
| `done` | Completed and verified |
The dashboard renders these visually so the active item is always obvious at a glance.
Example
Say you ask Revix to build a coin pickup system. It might emit a checklist like:
| # | Item | Status |
|---|---|---|
| 1 | Create `Coin` template Part in ReplicatedStorage | `done` |
| 2 | Add ParticleEmitter and Sound to the coin | `done` |
| 3 | Write `CoinService` ModuleScript in ServerScriptService | `in-progress` |
| 4 | Create `OnCoinPickup` RemoteEvent | `pending` |
| 5 | Write client pickup handler | `pending` |
| 6 | Wire up leaderstats integration | `pending` |
As work progresses, items flip from pending to in-progress to done. If something fails, the failing item stays in-progress and the AI explains what went wrong before deciding whether to retry or replan.
Interrupting and redirecting
You can interrupt the AI between items by sending a new message. The current in-progress item finishes (or aborts at a safe point) and the AI re-plans from your new input.
Useful phrases:
Stop. Don't add the leaderstats integration — I want a different stats system.Wait — before you write CoinService, let me show you our existing pattern. Read ReplicatedStorage.Modules.PlayerService first.Skip step 4, we already have a RemoteEvent named CoinPickup in ReplicatedStorage.Events.The AI updates the checklist to reflect your new instructions before continuing.
When the AI does and doesn't use checklists
Checklists appear for long, multi-step tasks. The AI judges whether the work justifies one — single edits, quick property changes, and one-shot generations skip the checklist and just run.
You can also ask explicitly.
Plan this out as a checklist before you start.Don't bother with a checklist, just do it.Troubleshooting
- Checklist gets stuck `in-progress`: a tool call may have errored. Look at the AI's most recent message — it usually explains. Tell it to retry or skip the item.
- Checklist is too granular: ask for a higher-level plan ("plan this in 3-5 steps, not 20").
- Checklist is too vague: ask for a more detailed breakdown before starting.
- For interrupting mid-stream, see Chat Basics.