Artifacts are review attachments produced during a task. They help you confirm what changed before you spend time digging through code.
Common artifact types
- screenshot of a key UI surface
- short screen recording of an end-to-end flow
- log or text report with the exact output you want to inspect
- generated file you want to review before accepting the task
How to use artifacts well
- Ask for the artifact in the task or follow-up message.
- Open the artifact pane and compare it to the requirement you care about.
- Request a revised artifact if the result is incomplete or incorrect.
- Use the artifact alongside diff review, not instead of diff review.
When artifacts help most
- UI or styling changes
- setup or onboarding flows
- browser automation results
- validation summaries that are easier to scan than raw terminal output
Useful request examples
Attach a screenshot of the updated settings page after the change.Attach a short text report that lists the commands you ran and whether they passed.