Get started
What inline does
inline reads the whole codebase around a change before it comments. Here is what it produces on a pull request, and where to find each part of it afterwards.
#When inline runs
Open a pull request in a repository where reviews are on, and inline picks it up. It runs again on every new push, when you mark a draft ready, and when someone reopens a closed pull request.
Drafts wait until you mark them ready. To turn reviews on for a repository, see Enable a repository.
#What inline posts
A review arrives on the pull request as a summary comment, plus a finding on each line worth commenting on. Every finding has a severity, a category, and the evidence behind it. Findings explains how to read a finding and what to do about it.
When a review finds nothing, it posts no comments and shows a clean verdict in the portal.
#Why some pull requests get more attention
Every pull request is triaged first. A change that a deeper read would add nothing to gets a Trivial verdict and stops there. A change that warrants more gets the full pass, where inline reads the surrounding code, follows call sites, and checks its own claims before posting.
That is why a dependency bump comes back in seconds and a rewrite of the payment path takes longer. How a review works explains each verdict.
#Where each part shows up
Reviews
Every pull request the agent has processed, newest first. Open one to see posted findings, suppressed findings, and cost.
| Pull request | Verdict | Findings | Cost | When |
|---|---|---|---|---|
| inline#482Cache review results per head SHA | Substantive | 3 | $•.•• | 2h ago |
| inline#481Bump tedious to 18.6.1 | Trivial | 0 | $•.•• | 5h ago |
| inline#479Rework the merge gate summary | Substantive | 1 | $•.•• | yesterday |
| On the pull request | In the portal |
|---|---|
| The posted review and its findings | Reviews, one row per pull request |
| A comment you addressed to @inline | Conversations, with what you asked and what inline answered |
| The inline / review check in the merge box | Review config, where you set its mode |
| A rule you taught with @inline learn | Learnings, where you approve and scope rules |
#What inline watches between pull requests
The Security, Runtime & cloud and AI assurance groups in the rail run on their own schedule rather than on a pull request. Each is switched on separately: repository security, CI/CD runs, runtime errors, cloud posture, prompt quality, and vendor agreements.