Inspection
Inspect files in the right order
Start with the file tree, then open the file that answers the current question.
Use the explorer first
Check what the agent created or touched before reading one file in depth.
Open the exact file you need
File-operation cards and chat references help you jump to the relevant implementation quickly.
Use the header path as confirmation
The breadcrumb makes it clear which file you are reviewing.
Cross-surface flow
Let chat narrow the code review surface
`Code` is easiest to use when chat already told you where to look.
Start from file-operation groups
They give you the smallest believable list of touched files.
Open only the file that answers the current question
Avoid turning each run into a full manual code audit.
Use `Code` to confirm implementation, not to reconstruct the whole run from scratch
Chat should tell you why something changed; `Code` should show exactly how.
Responsive behavior
Understand compact code layout
Desktop keeps files and editor together
You can browse and inspect side by side.
Compact mode splits `Files` and `Editor`
Smaller screens keep each surface usable by separating them.
The responsibility stays the same
`Code` is still the place to confirm implementation details.