When does a review trigger?
ByteRover evaluates every curation operation and flags it for review based on two criteria:
The curation agent determines impact level for each operation. A high-impact change is one that would meaningfully alter the meaning or direction of your stored knowledge — for example, replacing “we use Redis for caching” with “we use Memcache for caching.”
Changes flagged for review are already written to disk. Review lets you keep or roll back the change — it does not block the write.
What gets flagged
Any of the five curation operations can trigger a review:- DELETE — Always flagged, whether deleting a single file or an entire domain folder.
- UPDATE / UPSERT — Flagged when the change is high-impact (e.g., changing core technology, contradicting previous knowledge).
- MERGE — Flagged when combining files involves high-impact content changes.
- ADD — Rarely flagged, since new knowledge typically doesn’t conflict with existing content.
Review lifecycle
- The change is live locally. Your context tree already reflects the new content. Queries return the updated knowledge.
- The change is blocked from push. Files with pending or rejected reviews are excluded from
brv pushuntil resolved. - A backup exists. ByteRover stores the pre-change version so it can restore the file if you reject.
How you’re notified
Where you see pending reviews depends on how the curation was triggered:
Whichever path triggered the curate, pending edits also show up inline in the Changes tab of
brv webui (when running), with op-type and impact badges next to your other diffs. Dashboard notifications deep-link to that tab with the right project pre-selected.
What happens on approve vs reject
For DELETE rejections, the deleted files are restored to disk. For MERGE rejections, both the target file and the deleted source file are restored.
Next steps
Manage Reviews
Approve, reject, or selectively review changes via CLI and web UI
Agent Review Workflow
How coding agents discover and handle reviews on your behalf