Glossary

Admin / viewer. Your role in a Gryndel workspace. Admins can change settings; viewers can see everything but change nothing. On GitLab, the group's Owners and Maintainers start as admins; on GitHub, the account's owner or the organisation's owners do. See Members and roles.

Agent. In the Agents review mode, a specialist reviewer with its own instructions, such as "security" or "database and migrations". See Review agents.

Commit status. The pass/fail mark GitLab or GitHub shows next to a commit, merge request or pull request. Gryndel sets one to tell you whether the review found blocking problems. On GitHub it's the gryndel/review status check.

Finding. One problem Gryndel reports, posted as its own comment thread on the merge or pull request. Each has a severity and a location in the code.

GitHub account. On GitHub, an organisation or a personal account, which owns repositories. A Gryndel workspace on GitHub belongs to one account: the one that installed Gryndel's GitHub App. Accounts don't contain other accounts, unlike GitLab groups.

GitHub App. How Gryndel works on GitHub. Your operator registers an App on GitHub (or GitHub Enterprise Server) and an account installs it on some or all of its repositories. Gryndel can then read those repositories, receive their webhooks, and comment as the App's bot, shown as <app name>[bot]. The App also lets you sign in to Gryndel with GitHub.

GitLab group. A folder on a GitLab server that holds projects and subgroups. A Gryndel workspace on GitLab belongs to one root (top-level) group.

Merge request (MR). GitLab's name for a request to merge one branch into another, where people discuss and review the change. GitHub calls this a pull request. Gryndel reviews both.

Model / provider. The model is the AI that reads the code. The provider is where it runs: a hosted service such as OpenRouter, OpenAI or Anthropic, or a model server you run yourself. See Model settings.

OAuth application. A registration in GitLab that lets Gryndel's web app ask "who is this person?" when you sign in with GitLab. Your Gryndel operator set it up. Signing in with GitHub uses Gryndel's GitHub App instead.

Pull request (PR). GitHub's name for a request to merge one branch into another, where people discuss and review the change, numbered like #12. GitLab calls this a merge request (!12).

Review mode. How thoroughly Gryndel reviews: single (one pass), verified (a second pass checks every finding) or agents (several specialists, then verification).

Rule. An instruction every review follows, such as "new endpoints need an integration test". See Rules & learnings.

Reviewer account. The GitLab account Gryndel reads code and posts reviews as in a workspace: a user made for Gryndel or a group access token, whose token the workspace's admins give Gryndel. On GitHub, Gryndel posts as the bot of its GitHub App, shown as <app name>[bot].

Service account. An account that is not a person. Where an operator allows it, Gryndel's shared GitLab account (usually gryndel) reviews workspaces without their own reviewer account.

Severity (P0–P2). How serious a finding is: P0 is critical (security or data loss), P1 is realistic incorrect behaviour, and P2 is a minor real issue. By default, only P0 fails the commit status.

Webhook. An automatic message GitLab or GitHub sends to Gryndel when something happens, such as a new merge or pull request, a new commit, or a comment. On GitLab each enrolled project has its own webhook; on GitHub the GitHub App's single webhook covers every repository it is installed on.

Workspace. Gryndel's space for one GitLab group or one GitHub account: its repositories, settings, rules, models and history. You see only the workspaces of the host you signed in with.