Full-file scan (ocr scan) will land slightly later than planned

[css521]

Hi everyone,

A quick heads-up on the upcoming full-file scan capability (ocr scan) — the mode that reviews entire files instead of git diffs, intended for auditing unfamiliar codebases, pre-migration sweeps, and directories that have no meaningful diff.

The feature is actively in development and largely working today. It's being tracked in PR #93. However, due to current resource constraints on our side, merging it into the main release will be slightly delayed. We'd rather ship it once it meets the same quality and stability bar as the existing diff-review flow than rush it out before it's ready.

What this means for you:

• The diff-based ocr review workflow is unaffected and remains fully supported.
• ocr scan will follow shortly — we'll post timeline updates in this thread as the schedule firms up.

Want to try it now? (early access)
If you'd like to use full-file scan before it lands upstream, you can build and run it from this fork:

👉 https://github.com/css521/open-code-review

git clone https://github.com/css521/open-code-review
cd open-code-review
go build -o ocr ./cmd/opencodereview


# scan the whole repo (or a path), works in non-git dirs too
./ocr scan
./ocr scan --path internal --preview

Feedback from early testing here is especially valuable and will directly help us finalize the feature.

Thanks for your patience and continued interest!

— The Open Code Review team