Continue after an error

A long job can stop halfway because of something that has nothing to do with your work: the model is at capacity, the server is overloaded, the network dropped, or the tool's program ended. Without help, the session sits there until you come back and type "continue". AigoPilot can do that for you. When a turn of Claude Code, Codex or Grok stops on an error where trying again makes sense, the studio waits a little and continues the same session by itself, with the same model and the same settings.

It applies to sessions the studio runs. A session open in VS Code or a terminal is that program's to continue.

What you see while it waits

A line under the conversation says what happened and when the next try is, for example "Codex stopped on an error. AigoPilot continues it at 15:41 (try 3 of 10)." Under it stand the tool's own words, so you can read the error itself. Two buttons sit beside it: Try now continues at once, and Stop the retries ends the waiting for this session.

While it waits, the session counts as working, so you do not get a notice for every failed try. When the studio gives up, the session shows as stopped midway, you get the ordinary notice once, an alert stands in the column, and a note in the conversation says how many times it tried and what the tool said last.

How often it tries

The pause grows after each failure in a row: 1, 2, 5, 10 and 15 minutes, then every half hour. When the error is a usage limit and the tool said when it resets, the studio waits until then and one minute more.

A try that moves the work forward, where the model writes something of its own or a tool gives a result, starts the count again. The cap counts tries in a row that move nothing forward. It is 10 unless you change it. Since your last prompt the studio never continues more than three times the cap, progress or not, so a session cannot loop for a day.

A prompt of your own ends the waiting and starts the count again from it. So does stopping the turn, refusing a permission, or closing the session.

Errors it never continues

Some stops cannot be helped by another try, and the studio leaves those alone: a refusal for safety or policy, a problem with sign-in or billing, a conversation that no longer fits the model, and a request the tool calls wrong. The conversation then says that AigoPilot does not continue this session by itself, with the tool's words.

The studio knows the usual messages of the three tools. A message it has never seen is judged once by another subscription of yours, a different tool from the one that failed, or by a key of your own kept in the studio. The answer is kept, so the same message is not asked about again. While that question is out, nothing is continued. With nobody to ask, the studio treats the error as one worth trying again, inside the cap.

Turn it on or off

1. Open Settings, then How sessions work.
2. Under When a turn stops on an error, choose Continue by itself or Wait for me.
3. Set Continues in a row without progress, from 1 to 50.

A project can differ from the rest: its settings have After an error, and what you choose there wins for that project. It is on by default.

A Claude Code session that reached its usage limit with a known reset time keeps its own setting, described in When you hit a usage limit. If a studio restarts while a session waits, it takes up the wait again; such a session is resumed with its account and the tool's default settings.

Small tips

Questions