VyroAI

Loading...

When a Generation Is Cut Off

You pressed Stop, closed the tab, or the answer stopped mid-file — what you pay, and how to pick it back up.

The work does not stop when you leave

A generation runs on the server, not in your browser, so closing the tab, locking your phone or turning it sideways does not kill it. What you lose is the view of it.

Come back to the project and the Code Studio checks for a job that was still running and shows you where it got to.

Stop is the one thing that does stop it

Pressing Stop is different from leaving. While the AI works, the send button at the bottom-right of the message box turns into a red square (its tooltip reads Stop generating). Press it and the run stops on the server too: no new file is started, and you pay only for the work that was already done. Files that were finished stay in your project.

The reply ends with one line saying what happened: "You stopped this run before anything was built.", or, when some files were already written, "You stopped this run before it finished. Send "continue" to resume."

The credit figure under the reply counts the whole run as one number: the planning, every file, any repair rounds, and whatever was settled after you pressed Stop. When a turn has several replies, the total sits under the last one and the earlier ones show —, so nothing is counted twice.

The "While you were away" card comes first

Before either banner below, the top of the chat may carry a card headed While you were away. It is the first thing to read when you come back, because it is a summary rather than a question: how long you were gone, and which files were written and put into your project while you were.

If nothing had been written yet it says so plainly — "No files had been written yet, so nothing was lost." — which is the answer people are actually looking for.

Two buttons where they apply: See the files opens what changed, and Finish it picks the job back up if there is more to do. The × dismisses the card; it is a summary, so dismissing it throws nothing away.

The "Generation in progress" banner

Above the chat you get a banner with the phase it reached — Planning, Analyzing files, Creating files, Streaming changes — a progress bar, and a count of the files it had finished.

Once the job is more than a minute past its start, the banner turns amber and reads Generation running in background. That happens to every job that runs longer than a minute, whether or not it is still writing, so amber on its own does not mean it has stopped.

Two controls sit on it:

The "previous response was cut off" banner

A different case: the answer itself stopped halfway — the network dropped mid-sentence. Then a banner appears above the message box saying The previous response was cut off, with a Continue generation button.

Pressing it asks the AI to carry on from where it stopped rather than starting the whole job again, so you are not billed twice for the part that already worked. You can dismiss it with the ✕ and simply type instead.

"Send continue" is not paid twice

A very big job can end on purpose, with a message that the project is bigger than one run and a list headed Still to do. The run stopped at a safe point: the files on that list were never started, so they were never charged.

Send continue and the next run picks up with the files still on that list. The files already written are not written again, and you do not have to describe the project again. You pay for the new run's work, not a second time for what was already done.

Half-written files are thrown away, not stored

A cut-off generation used to be able to leave one file half-written. Today the Code Studio checks each new file for completeness: a truncated file is thrown away rather than stored, and a message tells you which ones went — "the stream cut off before these finished, so they were not kept. Re-run the request to generate them fully."

Nothing carries on by itself here, so send the request again for the files that were dropped. If something still looks wrong after a messy interruption, Version History is the way back.

A message that never sent is put back in the box

A different kind of interruption: the message never left at all. The connection dropped before any answer started, and an error says so.

The text you typed is not lost. It goes straight back into the chat box, and the error message tells you which of three things happened:

A kept message survives a reload, an update of VyroAI and closing the project: reopen it and the message is waiting in the box, in the mode you sent it in — a Build message comes back as Build. It is never sent by itself, so nothing is spent until you press send. It is kept in that browser, for that project, for up to a week, and it is cleared the moment a message in that project does get through.

The update bar says so too when there is one: A new version of VyroAI is ready — your unsent message will be kept.

Nothing marks a quiet job failed by itself any more. When you open the project and its newest run is more than three minutes old with nothing to restore, a note says Previous generation timed out and you simply send the request again; a banner that will not clear is safe to cancel with the ✕.

Where to next

20 of 37 in Code Studio (IDE) · Last checked 12 September 2026 · Previous: The Report After a Run