When the agent stops, and retrying
A line at the end of the transcript when the agent process died, a turn logged an error, or the thread is waiting out a usage limit. It says what happened and offers one button to pick the work back up.
Why you would use it
An agent that crashed used to be a silent red dot. This is the line that says why, and the one tap that restarts it.
How to use it
When the line appears, read the sentence and the grey detail under it.
Tap
Retryon the right (orRetry nowwhile paused) to resend your last message. That also restarts a crashed agent — the vendor session is resumed, so the conversation is not lost.
What you see
One line at a time, between two hairlines. The icon on the left and the sentence say which case it is:
| Icon | Sentence | Means |
|---|---|---|
| amber ring | Codex usage limit reached. Your queue will pick up at 18:40. |
the plan's quota is spent; VCode will resume on its own |
| red stop square | Claude stopped after 4 tool calls. |
the agent process exited or failed to start |
| red stop square | Claude hit an error. |
the turn logged an error |
| red stop square | Claude is logged out on devbox. |
the agent's login expired or is missing; Log in to Claude replaces Retry (log-in-to-an-agent) |
The sentence names the agent. after N tool calls counts the tool calls since
your last message and is left out when there were none. Under the sentence, in
grey, the detail from the vendor, cut at 400 characters.
A usage pause puts the window and the queue in the detail, for example
5-hour window · 2 messages waiting, or resumes on its own when there is
neither. The time left sits in amber on the right, 47m or 1h 12m, beside
Retry now. Once the time has passed the sentence reads
… usage limit reached. Your queue picks up now. and the countdown goes.
The status bar carries the short form:
⚠ stopped in red, tappable for the detail, and ⏸ resumes 18:40 in amber
while paused.
The line goes the moment a new turn starts, so it is always about right now. There is nothing to dismiss.
Limits and known gaps
Retryis offered only when there is a message of yours to resend. It is hidden when a start failed and left messages queued — retrying would send an older message and both would go once the thread starts. A usage pause keeps the button, because the queue behind the pause is what it resumes.- A stop reason is not a fault signal. Each vendor names normal completion
differently (claude
end_turn, codexcompleted), so the line only appears on a real process fault or a logged error. /cleartakes the line with it: the failure belonged to the conversation that just went.- The detail comes from the vendor. It can be terse.
Related
- activity-line — the line while the turn is still alive
- hand-a-tab-to-another-agent — the refusals a handoff can produce
- read-the-transcript — where the line sits
- usage-limit-pause-and-retry — what the amber line is waiting for
- resume-after-a-restart — the turn a restart cut short
- status-bar — the short form of the same state
- toasts — how a server refusal reaches you
- log-in-to-an-agent — the line for a logged-out agent