Skip to main content
Review the run, not just the diff. You already read the diff and run the tests — that’s what the code says it does. Garnet adds the second pass: what the code actually did when it ran. 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. The diff shows intent. The Run Profile shows what happened.

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.

​
Two passes on every PR

Pass 1 reads the diff and reasons about intent — you and your AI reviewer. Pass 2 watches the run and reports behavior — Garnet. Execution is the new code; the Run Profile is its commit. Garnet doesn’t replace your AI reviewer or static analysis. It sits beside them and gives them ground truth: what the code actually did when it ran.
Garnet's second pass on a PR: a new egress the diff didn't show, traced to the process that made it
Garnet’s second pass on this PR: an outbound connection the diff never showed — chainstack.com, traced to wget in the workflow. More write-ups →

​
Vocabulary

Five terms carry the whole product. Every page uses them exactly this way.
TermMeaning
runOne monitored execution — a CI job, workflow run, or agent run. The event.
Run ProfileThe record a run produces: process lineage, network egress, and file access, tied to the commit. The product noun.
runtime checkAn invariant evaluated against a Run Profile → pass or fail.
detection signalA low-level Jibril event (dropdomain, hidden_elf_exec…) that composes into checks.
Run Profile stateHow the result reads on the PR — Clean or Needs review.

Install Garnet

Two clicks from a workflow to your first Run Profile on a PR.