Skip to main content

​
Overview

Change reviews let you approve or discard changes to a file before they’re applied to your context repository. Use them to keep sensitive files under human control while everything else stays self-maintaining. Reviews happen in the Changes tab. Select a change from the list to review it.

​
Requiring review

Review is set per file. Open a file’s settings and turn on Require review. From then on, any change to that file is held for review instead of being applied automatically. Requiring review is a governance control, so it’s available to members who can manage access on the file.

​
Reviewing a change

The Changes tab has two lists:
  • To review: changes waiting for a decision
  • Completed: changes that were approved, discarded, or cancelled
Each change shows a change summary with an explanation of the change, its status, when it was created, and the sources it’s based on, followed by the file diffs. A change is one of two types:
  • Automated change: produced from a connected source
  • Manual update: a direct write to the file, made in the platform or through MCP or the API

​
Approving or discarding

For a change that’s in review, you can:
  • Accept changes: the change is applied to the file
  • Discard: the change isn’t applied. A reason is required and kept on the record for that change.
Multiple changes in To review can be selected and discarded together using Cmd + click. Discard reasons are visible in the details of completed changes. If the files in a change are deleted before it’s reviewed, the change is cancelled automatically and no review takes place.

​
Resolving a change via chat

If a change conflicts with the current file, Accept changes points to Resolve via chat. Open it from the change in the Changes tab to start a conversation with a context agent. The agent can compare the proposed change with the current file, ask how to handle conflicts, and confirm the combined text before applying the resolution. The resolved change then appears in Changes.