Supervision means watching the agent’s direction, permissions, and evidence instead of waiting only for its final message. Review its plan, inspect important tool calls, answer real ambiguities, and stop the run when it repeats failures or expands beyond scope.
Good supervision does not require approving every harmless file read. Set safe defaults and reserve attention for writes, network access, new dependencies, destructive commands, and design choices. Ask for checkpoints on long tasks and keep git changes visible. Do not rescue the agent by giving vague encouragement; provide concrete evidence or a corrected constraint. The supervisor remains accountable for deciding whether the work is safe, complete, and understandable enough to merge.
This answer doesn't lend itself to a diagram - it reads best . No credits were charged.
Why there's no diagram: “”
The interactive diagram is below the answer - jump to diagram ↓ · Below it, the related concept . Jump to it ↓
The diagram below the answer is the concept . Jump to it ↓