Skip to main content
November 4, 2026
A GitHub pull request where the paradime-eu bot posted a DinoAI review from a custom reviewer named bugbot: a summary with 1 finding, and a high-severity inline comment on dim_f1__constructor.sql explaining why the new cutoff makes a CASE branch unreachable
In September, the DinoAI GitHub Action let you run an agent on pull requests from a GitHub Actions workflow, with an Account API key stored as a repository secret. Paradime now runs your agents on pull requests itself, through the Paradime GitHub App. You don’t need a workflow file, a runner, or an API key.
  • Your agents as reviewers. In the Agent app, open Code review and add a reviewer. Pick Custom reviewer and choose any of your agents, for example the end-to-end PR reviewer or the impact assessor. It runs on every pull request into its target branches, posts its findings as one GitHub review, and reports a Paradime Code Review check you can require before merging. See Custom reviewers.
  • Ask DinoAI in the pull request. Comment @paradime with a question on a pull request, or in a review thread on a changed line. DinoAI starts a session on the pull request’s head commit and replies in the thread. Later mentions continue the same session. @paradime review runs your reviewers on demand. See Mention @paradime.
  • Sessions you can follow. Review and mention sessions show in Sessions with the repository and a link to the pull request, and Turbo CI runs show which reviewer reviewed the change. See Agent sessions.
The DinoAI GitHub Action still works. Keep it if you want the review to run inside your own workflow. See PR reviewer with the GitHub Action. Shipped in Paradime v6.24.0.