What changed. What it means for you.

Repository scans and GitHub automation controls

September 20, 2026 · Web update

Repository scans now save a commit, inspected-file coverage, findings and explicit skip reasons. AI scans show partial coverage when the context budget excludes files.

Automations adds installation setup, per-repository controls, coding-request history and AI usage records. The bot requires GitHub App registration and installation before it can publish. Suggested fixes remain subject to human application and testing.

Managed AI reviews are available

September 19, 2026 · Website

Signed-in customers can request an AI review for a connected GitHub pull request. Results are saved with the reviewed revision. Exact source-reference validation rejects malformed responses; a failed review preserves the prior result.

A connected customer workspace

September 19, 2026 · Website

GitHub sign-in, repository selection, manual pull-request sync, personal triage, saved preferences, and scoped exports are available. Dashboard figures use connected workspace data and explain unavailable measurements.

A larger public resource library

September 19, 2026 · Website

Product, pricing and availability, review rules, resource, trust, and legal information now have dedicated pages. The blog launches with twelve practical articles for developers and reviewers.

Native scanner work remains in review

September 19, 2026 · Source development

Scanner fixes cover executable template expressions, sensitive source snippets, and CRLF diff parsing. Passing development checks and pushed source changes are separate from an installed Mac app release. No new signed or notarized public release is announced here.