Skip to content
Vekrun

Code reviews

Review where you write code.

Pull requests waiting for you, the diff, AI findings and your comments, side by side. Compare several models when a change is contested. You approve.

How AI Teams verify workReview docs
Reviews
#88 · src/auth/github.ts+42 −3
41 const token = await exchangeCode(code);
42- log.debug('oauth token', token);
42+ log.debug('oauth exchange ok');
43 const profile = await fetchProfile(token);
44+ const account = await linkOrCreate(profile);
45+ session.set(account.id);
46 return redirect('/');

AI findings · Claude, Gemini agree

SecurityThe token was logged at debug level before this change; make sure older log lines are purged too.src/auth/github.ts:42
CorrectnessThe callback does not compare the state parameter with the one issued at redirect.src/auth/github.ts:38
You

Please add the state check before merge. The token logging fix looks good.

Request changesApprove with comment
Approved by you · comment posted to the pull request

Product preview. AI review of local branches works in the development build; the pull-request inbox and GitHub/GitLab sync are planned.

Faster reviews, fewer tabs

Reviewing a teammate’s change should not mean leaving the place you understand the code best.

Planned Pull-request inbox and GitHub/GitLab sync.

  • One inbox

    Pull requests requested from you and the ones your teammates opened, in one list next to the code.

  • AI goes first

    Ask a model to look for security and correctness problems before you read a line. Findings point at file and line.

  • Compare models

    On a contested change, run a review council and see where Claude, Gemini and a local model agree and disagree.

  • You decide

    Accept or dismiss each finding, leave your comments, approve. Nothing is posted or merged on your behalf.

A review, start to finish

  1. Open the request

    The diff, the ticket it came from and the test results, in one view.

  2. Read the findings

    AI findings are suggestions with a location. Each one can be accepted into a comment or dismissed.

  3. Comment and approve

    Your comments go to GitHub or GitLab as yours. Approval is a button you press.

Where the pull request came from: the Board

Where this stands

Vekrun is in development. There are no public releases yet. AI review of local branches and diffs, and review councils across several models, work in the development build on macOS. The pull-request inbox, inline suggestions and GitHub/GitLab synchronisation are planned.

See the roadmap