Sessions and progress
Understand preparation, execution, follow-ups, and review.
A session keeps the objective, repositories, conversations, environment, and outputs for a piece of work together. It can contain several turns as you review results and ask for changes.
Read the visual explanation
Environment preparation finishes before the agent starts. The turn then runs, may wait for an answer, and returns a result for review.
Understand the milestones
| Milestone | What it tells you | What to do next |
|---|---|---|
| Input accepted | Uno recorded the request | Follow the existing session |
| Environment preparing | The machine and project setup are being readied | Read startup progress |
| Turn running | The agent is executing | Read activity or send guidance |
| Waiting for an answer | A decision or missing information is needed | Answer the questions |
| Turn completed | This execution returned a result | Review the summary, diff, and checks |
| Failed or interrupted | This execution did not finish normally | Inspect evidence and use recovery |
These are explanations of the lifecycle; individual status labels can differ by surface. Environment readiness and agent execution are separate. An empty conversation during preparation does not by itself mean the task was lost.
Work in a session
Start a session with the right repositories, branch, objective, and model. Add attachments when a screenshot, file, or clip supplies useful context.
During work, steer the agent and answer questions. Open progress and activity to understand steps, errors, and the final turn summary.
After work, review changes and pull requests, inspect app previews, and open published outputs.
Continue, stop, or recover
Sending a message to an idle session starts another turn. Sending guidance during active work adds input to that work; it does not instantly change files. Cancelling and archiving have different effects, described in session organization.
For failed or interrupted work, read startup and recovery before retrying. For programmatic acceptance and progress, use the MCP session workflow or Session API.