Session startup, interruptions and recovery
Find the failed milestone and recover accepted work without duplicating it.
Keep the existing session link when work is slow or interrupted. Inspect its state before resending the same objective or creating another session.
Start with the symptom
| What you see | What to inspect |
|---|---|
| Queued work | Whether input was accepted, other active work, and the displayed capacity or access message |
| Preparing environment | Startup progress, repository readiness, active manifest, and snapshot state |
| Model-access problem | The selected model, provider connection, and member model restrictions |
| Waiting for an answer | The session's clarification questions |
| Failed or interrupted turn | The last messages, latest successful step, and reported error |
| Completed turn with an incomplete result | The summary, failed or skipped checks, and a focused follow-up |
A ready machine is different from a running turn. A message can also be accepted before its turn is created. An empty conversation during startup does not establish that the request was lost.
Recover the existing work
- Read the latest conversation and progress state.
- Resolve the identified cause, such as a missing credential or failed repository setup.
- Use the retry, wake, or recovery action offered by Uno.
- Wait for the resulting state and follow the next execution in the same session.
- Inspect changes and external effects that may have happened before the interruption.
Cancellation is not rollback. A retry can continue from files or external work already created, so ask the agent to inspect the existing state when the previous result is uncertain.
Avoid duplicate work
If a send timed out, refresh the session and inspect accepted messages before sending it again. For API callers, retry the same logical request with its original idempotency key and body. For MCP callers, follow the acceptance workflow.
Ask for help with evidence
Include the session link, approximate time, last visible state, and relevant error. Mention the selected repository and provider without copying credentials or private log contents.
See progress, connections, snapshots, and preview problems.