Change review
Change review is the process of approving or discarding changes before they apply to a file in the context repository.
What is change review?
Change review is a process that holds changes to a file pending human approval before they apply. A file marked "Require review" queues every change (whether from an automated agent or a person) in the Changes tab, where someone with edit access can see the diff, approve it, discard it, or comment before it goes live.
Why do change reviews exist?
Not all files in a repository can handle automatic changes. Critical configuration files, compliance documents, or anything that shapes downstream decisions may need a human to see what changed before it applies. Change review lets a workspace reserve automatic changes for files that can tolerate them, while keeping stricter control where the cost of a mistake is high.
How does change review work?
To enable change review, open a file's settings and turn on "Require review." From that point, every change to the file, including agent edits, holds in the Changes tab pending approval. Someone with edit access opens the diff, reads what changed, and either approves it to apply, discards it to reject, or comments to start a conversation. Approved changes apply immediately; discarded ones disappear.
Change review respects access controls, so only someone with edit access to the file can approve or discard changes to it. If multiple people have edit access and changes are pending, each reviewer sees the same queue and can act on any pending change.