The configuration pull request is small enough to approve on a phone. That is exactly why it needs a better diff.
An agent setting can change which code runs, which credentials it receives, and whether a person must approve the next action. Line count says little about that authority.
Review this fictional change
The example below uses pseudoconfiguration rather than the schema of a specific agent:
reporting_tool:
- artifact: "<reviewed-digest>"
- credential: reporting-read
- filesystem: reports-read-only
- approval: required
+ artifact: latest
+ credential: developer-default
+ filesystem: workspace-write
+ approval: automatic
Four lines changed. Each line changes a different part of the trust decision.
The artifact floats. The reviewed code can be replaced without another configuration change. Resolve the actual version and digest before approval.
The credential expands. “Developer default” is difficult to review because its effective permissions depend on local state. Use a dedicated identity with a known scope.
The filesystem grant changes. A reporting tool now has write access. Ask which operation requires it and which paths should remain read-only.
The approval disappears. The same tool can act unattended. Evaluate the actions it can now take, including the arguments and destinations it controls.
Make those consequences visible in tooling
A useful configuration review highlights added tools, commands, modules, endpoints, credentials, writable paths, tool descriptions, and approval changes.
The Claude Agent SDK advisory shows how a seemingly ordinary value can affect command-line behavior and MCP startup. Reviewers need the resolved execution meaning of a field, not only its type.
Assign reviewers according to the capability being changed. A new cloud role needs its resource owner; a message-sending tool needs a recipient and data-flow decision.
Bind approval to a deployable bundle
Resolve dependencies and remote definitions. Record the effective manifest, configuration hash, and artifact digests together. Where signing is part of the deployment, verify the approved bundle before startup.
Observe the runtime state after deployment. Local overrides, cached artifacts, or a remote tool update can make the running system differ from the reviewed file.
Make rollback equally precise
Keep the last approved bundle available, including its artifact identities and policy. Rolling back only the YAML can leave a newer executable or broader credential in place.
The companion piece on configuration and execution explains why these fields deserve code-review discipline. This workflow makes that discipline practical for the person approving the next small diff.