Garnet Docs — The runtime review for your PRs

Code review has two passes now. Pass one: your AI reviewer reads the diff. Pass two: Garnet watches the run — recording what your code actually did when it ran (process lineage, network egress, file access) 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.

On this PR, the Run Profile recorded an outbound connection the diff never showed — chainstack.com, traced to wget in the workflow. More write-ups →

Vocabulary

Term	Meaning
run	One monitored execution — a CI job, workflow run, or agent run.
Run Profile	The record a run produces: process lineage, network egress, and file access, tied to the commit.
Runtime Review	The PR comment — one fold per recorded job, each with its process lineage and its recorded destinations. It records what ran; it does not judge. See Comment anatomy.
public run report	The shareable page a permalink opens — `app.garnet.ai/public/runs/<run-id>?profile=<profile-id>`. Public for runs from public GitHub repositories; sign-in required otherwise. See The public run report.
assertion	An invariant evaluated against a Run Profile. Each result is recorded verbatim — `PASS`, `FAIL`, or `ATTENTION` — in the run’s Assertions fold.
detection signal	A low-level Jibril event (`dropdomain`, `hidden_elf_exec`…) that composes into assertions.

Quick start

Get started

Reference

Overview

Quick start

The Run Profile

Vocabulary

Quick start

The Run Profile

​Vocabulary

Vocabulary