Long Tasks and Checklists
After this page you will be able to read everything Revix shows you during a long build, judge whether it is stuck or just busy, stop it safely, and pick a job back up after it ends early.
What you see while it works
A running job stacks up in a fixed order, top to bottom.
The thinking panel
Headed Thinking while it streams and Thought about it once the job ends, with a running clock and a word count. It is collapsed by default, with the last line ghosted underneath. Open it to read the whole stream.
Thinking is not progress. It is Revix talking to itself before it acts. While the panel is the only thing moving, nothing in your place has changed yet. That is normal at the start of a build and after a step goes wrong.
The checklist
On a job with real scope, Revix writes a checklist and keeps it up to date as it goes. Items move from waiting, to in progress, to done — or to blocked if something got in the way. It is the fastest way to see the shape of the work and how far through it is.
Small requests do not get one, because there is nothing to track.
The step timeline
A rail of rows, oldest at the top. Each row shows the action, what it acted on, and how long it took, plus a status dot:
- Blue and pinging — running now
- Grey check — finished
- Red triangle — that step failed
Click a row with detail to expand it. On a long run the middle is folded away behind an N more steps link so the rail stays readable, and the footer sums it up: how many steps, how many done, how many failed.
The live line and progress bar
While a step is running you get its verb, its target, an elapsed clock, a three-line scroll of the current thinking, and a step counter reading step N of 120. A progress bar sits at the foot of the job and runs to full when it lands.
How long is too long
| What you are watching | Normal | Worth acting on |
|---|---|---|
| A small edit or a question | Seconds | Over a minute with no steps at all |
| A screen, a system, a room | A few minutes | Nothing new in the timeline for several minutes |
| A generated map | Minutes — big maps at fine detail take several | See below |
| A whole landmark build | Many minutes and a long timeline | Steps repeating with no new results |
A few hard edges are built in, so a job cannot run away with your credits:
- A single Studio operation is cut off after 60 seconds. If that happens you get: "Studio stopped responding to that command. Make sure the place is still open and the Revix plugin is connected, then send continue."
- A whole job stops at 120 steps or one hour, whichever comes first.
- If six steps in a row change nothing, Revix nudges itself back on track, and if that does not work it ends the job rather than spinning.
Map generation is the one case where a long silence is expected. If it outruns the wait, you are told plainly that it is still building in Studio, with the last step and a percentage — that is not an error, and the map keeps building.
Stopping safely
The send button becomes a red stop button while Revix is working. Press it any time.
- Nothing is undone. Everything already built stays in your place: "Stopped. Everything built up to this point is saved in Studio."
- Stopping is handled on the server, so it sticks even if you close the tab straight after.
- If you want the work removed rather than paused, press
Ctrl+Zin Studio or ask Revix to undo it.
If your connection drops
You do not have to babysit a build.
- A dropped connection mid-step is retried automatically. This used to be the thing that made people type "continue"; now it usually fixes itself.
- Closing the tab does not kill a build. Reopen the dashboard and Revix reattaches to the run still in progress and replays what you missed, so you get the live tail back instead of a dead chat.
- If a job ends with nothing to show, you get a card headed That one stopped early with two buttons: Keep going and Start that again.
What "continue" does
Type continue and Revix picks up where it stopped, using its own record of what already landed. It does not start over and it does not re-do finished work.
| How it ended | What you see |
|---|---|
| Hit the one-hour cap | "Paused here — everything built so far is saved in Studio. Send continue to finish." |
| Hit the 120-step cap | "That was too big for a single run. Everything so far is saved — send continue, or split it up (e.g. build the UI then wire the scripts)." |
| You pressed stop | "Stopped. Everything built up to this point is saved in Studio." |
| Credits ran out mid-build | "You ran out of credits partway through. Everything built so far is saved in Studio — top up and send continue to finish." |
When a job ends early, Revix writes an honest account of exactly what landed and where. Read that list before you continue — sometimes the remaining work is better asked for as a fresh, narrower request:
The menu is there. Now wire the Shop button to open the shop panel.If you keep hitting the caps, the job is too big for one message. Split it: build the screens, then wire the scripts, then add the polish.