Skip to main content
Code review so far, as we know it, has been about reading the diff —what changed in code. But as you execute more and more code behind every PR––CI jobs, agent sessions, automation workflows––you’re blind to what actually executes.

Garnet watches the run — recording what your code actually did when it ran (process lineage, network egress, file access) at the system-level and posting the Run Profile back to the PR. The diff shows intent; the Run Profile shows behavior. AI is opening more PRs than anyone can read line-by-line, and dependencies, build tools, and agents run with the same access to your secrets as your own code. Garnet sits beside your reviewers and static analysis, and gives them ground truth from the run itself.

Quick start

Add Garnet to a workflow and get your first Run Profile in minutes.

The Run Profile

What you get back on the PR, and how to read it.
A Run Profile showing an outbound connection the diff didn't show, traced to the process that made it
On this PR, the Run Profile recorded an outbound connection the diff never showed — chainstack.com, traced to wget in the workflow. See some real examples of runs recorded by garnet →