Skip to content

Recover a Session

Return to the existing Session when a chat disconnects or stops. Its recorded conversation stays with it; you do not need a replacement chat.

  1. Open the ticket’s Now → Sessions section, or find the Session with ⌘K.
  2. Open the chat and read its status.
  3. Choose Resume for a recoverable Turn interrupted row, or Retry for a stopped or disconnected Session. If neither is offered and the composer is usable, send an instruction explaining where to continue.

Volli can automatically continue a turn interrupted by a recent process loss. It makes one attempt, only when the conversation reached a settled point with no unfinished tool call. It leaves the turn for you if you already continued it, another Session on the ticket moved on, or the loss was more than 12 hours ago. While the recovered turn runs, the row says Resumed after restart.

Resume continues from the recorded conversation without resending your last message. An unfinished tool call is recorded as interrupted rather than rerun automatically. Check the worktree before continuing: the original call may have changed files before the interruption.

Status What to do
Sign-in required Select Open settings, repair the provider connection in Settings → All projects → Models, then return and retry
Configuration invalid Select Open settings, fix the reported configuration, then retry
Disconnected Select Retry to reconnect
Reconnecting Wait while Volli retries; the row has no manual retry action
Rate limited Wait until the provider’s retry time, if shown, then select Retry
Session stopped Read the reason, then select Retry when it is resolved
Turn interrupted Select Resume if offered; otherwise send a new instruction
Waiting for an answer or Waiting for approval Respond on the question, budget request, or confirmation card
Quota exhausted Restore the provider allowance; retrying does not refill it
Context limit reached Start a new chat with a focused handoff; Volli has already tried summarizing this conversation

A provider failure can show a more specific headline, such as a refusal or an authentication error, instead of Session stopped. Read the detail beneath it before retrying. Dismiss hides a report; it does not fix the cause.

The interruption row records the cause a provider or transport reported. The same detail is available from volli session list and volli session peek <id>.

Cause Recovery
provider-refused Revise the task or choose another model; repeating the same request may be refused again
provider-overloaded Wait and retry, or choose another provider
rate-limited Wait for the stated reset; an exhausted allowance may require provider billing changes
auth-failed Repair the provider connection in Settings → All projects → Models
bad-request Fix configuration or reduce the request before retrying
context-overflow Start a focused handoff or use a larger-context model
network Restore connectivity, then retry
retries-exhausted Check the message and provider status before continuing
runtime-stopped Check connectivity and Volli’s local process health before retrying
unknown Read the available message; the provider did not supply a recognized structured cause

A Context limit reached headline still calls for a handoff when the provider classifies its response as bad-request. A deliberate Stop turn is separate from a provider failure.

If a stopped turn includes a future allowance reset, the row can offer Resume at… beside Retry. Select it to schedule one resume. The headline changes to Resumes at…. Use Cancel to withdraw it, or Retry to continue sooner.

Volli does not invent a reset time when the provider supplies none. A scheduled Session resume is separate from a saved Automation schedule.

Draft text and staged attachments survive navigation and relaunch while the draft remains open. If Volli had not accepted a message before an interruption, it can return above the composer marked Not sent. Use Edit message to bring it back into the composer, check its text and files, and send it again. Closing an unsent Chat Draft discards that draft.

Repairing a provider connection does not silently switch the Session to another model. See Models and usage to choose one yourself.

Existing Sessions keep their recorded tools and can gain additions at supported refresh points. Expand a Tools updated transcript row to see what changed. A new root Session receives the project’s current tool selection. Delegated helpers inherit their parent’s recorded MCP tools, so check the parent’s tools before delegating work that needs a newly added server.

Removing an MCP server can leave existing Sessions with unavailable tools. See MCP servers before deleting its configuration.