Read progress and activity
Use steps, activity, and summaries to understand what the agent did.
Open the session inspector's Progress tab for the current turn's steps and summary. The conversation also shows activity from the agent's work. These views help you understand progress without treating every log line as a final result.
Read the right evidence
| Surface | Use it for |
|---|---|
| Startup progress | Machine preparation, source setup, and execution readiness |
| Steps | The agent's planned or recorded work and its state |
| Activity | Tools, commands, reads, and other execution events |
| Turn summary | The agent's explanation of the outcome and remaining work |
| Changes and outputs | The files and results produced by the work |
Expand relevant activity for details. Older activity can load separately; if it fails to load, use the offered retry instead of assuming there was no earlier work. Timeline presentation can vary by release or workspace configuration.
Separate waiting from failure
During startup, the environment can be preparing before the agent emits a message. During execution, a long command may have little new output. A request for information needs your answer. A failed or interrupted turn needs inspection and recovery.
Read the actual error and the latest successful step. A command failure can be followed by a successful correction, so one red activity item does not establish that the whole task failed. Likewise, a completed turn can report checks that were skipped or could not run.
Verify a claimed result
For a reported test, inspect what ran and its result. For a code change, open the diff. For a UI change, inspect a preview. For a pull request, follow its link and read the review and checks there.
Use review changes for the delivery check and session recovery for interruptions. When asking for help, include the session link, approximate time, last visible state, and relevant error without copying credentials.