The verdict reaches your inbox the moment it lands on the pull request — the outcome, the finding that decided it, and what each engine found. There is nothing to set up and no recipient list to keep.
Get verdicts by emailWhat you get
Clear, Warning or Blocked, the Pulse, Graph and Probe lines, and one receipt — what you asked for, what your agent said, what actually happened. Enough to act on without opening anything.
No thresholds, no filters, no recipient list to keep current. The verdict goes out with the review — there is nothing to tune, and nothing to forget to tune.
The author and the reviewers get the same verdict at the same time. You never pick a recipient, because the people who need it are already there.
How to set up
Install the GitHub App
Add the Videlic App and grant access to the repos you want reviewed. There is no second install for email.
Connect your coding agent
One line connects your agent's sessions to Videlic — your key is included.
Open a pull request
Code as usual. No address to configure and no rules to pick — the verdict is in your inbox about a minute later.
Example
Videlic to you and 3 others
9:41 AM (1 minute ago)
Blocked
Your agent reported work as done that is not in the code. Plus 1 more issue that blocks merge. Not safe to ship.
Pulse 2 of 3 done, 1 reported done but missing
Graph 9 files touched, 1 finding
Probe 12 passed, 5 of 9 covered
Reported the auth tests updated — the suite was deleted
You asked: add rate limiting to the login route, and keep the auth tests green
Your agent said: Added the rate limiter and updated the auth tests — the suite passes.
What happened: the change deletes auth/login.test.ts and adds no test in its place. Confirmed by Graph and Probe.
auth/login.ts:34auth.tscheckout.test.ts:42Reviewed commit c1abcde.
Posted by Videlic — what your AI coding agent actually did.