Follow an active task
- Open the Code session and inspect its current state.
- Expand the activity or Worked details to see reported tool calls, commands, plans, and outputs.
- Open any approval or question card that is waiting for your response.
- Use the follow-latest control after scrolling back when you want to return to current output.
- When the run ends, read the final response together with relevant command results and changed files.
The amount of activity available depends on what the harness reports. A sparse tool row does not imply nothing happened. Likewise, a progress sentence or plan item is not evidence that the command finished successfully.
Inspect the work product
Use Files for saved content, Git for changes, Terminal for independent local checks, and Browser for a running preview. If an agent says a test passed, inspect the actual result or run the appropriate check yourself before relying on that claim.
Turn actions can provide copy, export, or read-aloud controls where available. Copying a response copies text; it does not capture every file or external artifact associated with the task. A read-aloud action uses its configured speech connection rather than the coding subscription.
Recognize incomplete endings
A stopped or erroring run can leave useful partial work and completed file changes. Review what finished before sending a recovery instruction. If submission or completion is uncertain, avoid duplicating a mutating task until the latest activity is understood.
See run and queue controls, Git review, and continuation recovery.