Sessions and progress
Start work, guide the agent, and inspect the result.
A session keeps the goal, repositories, conversations, environment, and outputs for a piece of work together.
Understand progress
Environment preparation and agent execution are separate. A ready environment means the agent has somewhere to work. Check the conversation's progress and messages to see whether work is queued, running, or finished.
Guide active work
Send a clear follow-up while Uno is working to adjust the approach or add context. Delivery of an instruction does not mean the change is complete; inspect the agent's response and final diff.
If the agent is idle, sending a message starts another turn. Cancelling work is a separate action from giving guidance.
Inspect outputs
Read the final summary, open linked artifacts, and compare the diff with the requested outcome. Check which tests ran, which failed, and which could not run. A pull request still needs the review and release checks your team normally uses.
Recover work
If a session reports a failed or interrupted turn, inspect its latest messages before retrying. Use the recovery action offered by Uno. Avoid creating another session for the same goal until you understand whether the first one accepted the work.
For programmatic startup and recovery, follow the MCP session workflow.