Understand what happened during a task
A teammate can report progress while it works and show activity from the tools it uses. Use those details to understand the result and any unfinished steps.
Read the outcome first
The final reply should explain what was produced or changed, what checks ran, and what still needs input. Open the file, link, or task card that represents the result.
Progress narration explains the ongoing work. It is not by itself evidence that a file was saved, a message was sent, or a change was published.
Inspect tool activity
Expand the activity summary to see the tools and actions used. Failed actions and requests for approval are called out. Some connection failures provide a Reconnect action; an approval-required entry points you to the request in chat.
Open Workspace → Activity for a view of activity across your teammates.
Continue from a partial result
Tell me which steps completed, which failed, and which are waiting for me. Link the outputs already created. Continue only the unfinished steps once the missing access is restored.
For cloud coding, check the verified GitHub link and commit before treating publication as complete. For a scheduled task, inspect the run's result rather than only the saved schedule.
If a task appears stuck, start with troubleshooting and preserve the existing conversation so the unfinished work remains identifiable.