What’s new in HeyDeer

Choose Set up repository checks under Getting started, and HeyDeer opens a pull request that adds checks based on your code and past pull requests. To use your own coding agent instead, copy the prompt.

When a workspace runs out of credits, the link in HeyDeer’s PR comment opens Usage & billing with the options ready: choose a plan, upgrade to Pro, or add credits.

Each finding shows what’s wrong and what it causes, with any suggestion you can commit. Why it happens and the suggested fix are under Learn more.

MCP servers are now connectors. Fix with HeyDeer and @heydeer mentions can use them too, you choose which tools each one allows, and reviews only call read-only tools. Each review and task page lists its connector calls.

Put review-only guidance in REVIEW.md, at the repository root or in any directory. HeyDeer follows the files that cover a PR’s changes, so teams coming from other code reviewers can keep theirs.

Choosing findings to fix, starting Autopilot and following a task or run happen beside your reviews, on pages laid out like the review page.

HeyDeer leaves approval of a PR that changes review guidance, such as AGENTS.md, CLAUDE.md, repository checks or skills, to a person.

While a review runs, expanding a reviewer on the review page lists the potential issues it reported, before verification.

HeyDeer runs the checks whose frontmatter has a files key and ignores checks written for other review tools. It skips an invalid check and names it under Review notes.

Message the HeyDeer team from the chat button on the website, or from Contact support in your account menu. When you’re signed in, your conversations follow you to any browser.

Select code or text in a walkthrough and choose Ask HeyDeer. HeyDeer reads the PR’s code to answer, and you can ask follow-ups. Questions stay private to you and are never posted to GitHub.

Each finding names its category after its severity, on GitHub and on the review page: correctness, reliability, security, performance or maintainability.

HeyDeer moves on as soon as the code is ready, so reviewers usually start working up to 30 seconds earlier.

HeyDeer posts the review on GitHub as soon as it is ready, and the walkthrough follows a few minutes later.

The review page shows whether a PR qualifies for automatic approval beside its risk level, with the reasoning one click away. Feedback scope previews now sit beside the findings they change.

The review page charts every stage and reviewer on one timeline and shows what each running reviewer is working on, in its own words.

When a GitHub Actions check fails, Autopilot reads the failed step’s log to fix the cause. An owner of the GitHub account first approves the Actions permission on GitHub.

It matches the HeyDeer homepage, and the sidebar groups Reviews, Autopilot and Tasks, then Insights, then your workspace.

Ask @heydeer on a pull request to resolve its conflicts, and HeyDeer merges the base branch into the pull request’s branch and pushes the result. Pull requests from forks still need their author, because HeyDeer can’t push to a fork.

Walkthrough tabs whose changes span several parts of the system, such as the browser, a server and a database, now open with a diagram of how those parts connect or the steps between them.

Start Autopilot from a review or comment @heydeer autopilot. HeyDeer fixes findings, failing checks, merge conflicts and requests from people with write access, pushes to the PR’s branch and reviews each change until the PR is ready.

Mention @heydeer in a pull request or issue to ask about the code, have HeyDeer change it, open issues or start a review. HeyDeer answers where you asked, and each request appears under Tasks.

Reviews now come with a walkthrough: related changes grouped together and important changes highlighted, with the code for each group. Open it from the Walkthrough button on a review, and mark a whole tab as Viewed when you’re done.

In Balanced and Detailed, HeyDeer also points out low-cost improvements it has verified, such as unused code, duplicated logic, comments that contradict the code and tests that can’t catch what they check. It leaves out cosmetic nitpicks.

When a pull request changes a plan, a specification or AGENTS.md, HeyDeer works through what following it would do and reports cases it leaves open or contradicts.

See findings by severity, how many your team fixed or declined once HeyDeer checked again, and totals for each repository. Workspace admins also see totals for each author.

HeyDeer reports minor issues, such as mismatched copy, as Low. Concise leaves them out unless a repository check raised them, and Detailed also includes likely ones for coding agents to verify and fix.

When HeyDeer agrees with a concern in another reviewer’s inline conversation, it posts its own finding.

When a pull request corrects a problem, HeyDeer points out other places in the code where the same problem remains.

When a finding depends on how a library, API or platform behaves, HeyDeer checks its official documentation or published source.

HeyDeer writes each fix PR’s title and description from what it changed and the tests it ran.

Right after setup, HeyDeer asks whether to review pull requests on every push and shows which repositories that covers.

By default, HeyDeer doesn’t review dependency updates from Dependabot, Renovate, pre-commit.ci and Snyk on its own. Comment @heydeer review to review one.

HeyDeer skips changes to lock files such as pnpm-lock.yaml and Cargo.lock, so dependency changes use fewer credits. Mark a lock file -linguist-generated in .gitattributes to review it.

When HeyDeer doesn’t review a commit automatically, the HeyDeer Review check’s title names the reason, such as reaching Maximum automatic reviews per PR. Its summary says how to request a review.

In public repositories, HeyDeer shows what a free review would have cost. Reviews over the fair-use limit use workspace credits, like reviews of private repositories.

When a later review of a PR doesn’t approve it, HeyDeer dismisses its earlier approval and links to the new review.

HeyDeer shows the last 30 days of reviews by default. Choose a date range, filter by repository, status, result or author, and browse older reviews page by page.

HeyDeer reviews public repositories for free within fair-use limits. Sign in with GitHub and add a public repository to start, with no application.

Each repository runs as many reviews at once as your plan includes, independently of your other repositories.

HeyDeer accepts @heydeer review anywhere in a new PR comment or inline review comment, alongside your explanation.

Completed, failed and canceled reviews keep a Review activity panel with each stage, how long it took and what every reviewer did.

Reviewers describe what they’re working on in the repository’s review language and show how many potential issues they found before verification.

Select Fix with HeyDeer in a review comment, pick the findings to fix and add instructions if you like. HeyDeer opens a separate pull request against your PR’s branch, including GitHub Actions workflow changes, using workspace credits.

The review page shows each reviewer under its stage, with its current activity and an expandable history.

HeyDeer rates every PR as low, medium or high risk and explains why. Under PRs HeyDeer may approve, choose the highest level it approves; the rest wait for a person.

Set Remaining issues to Allow Low issues to approve a PR when only Low issues remain. HeyDeer still lists them.

The check shows the total, queue and review time.

Review comments end with a collapsed section showing the review depth, what started the review, and links to the full report and settings.

Automatic reviews start as soon as GitHub reports a new or updated PR.

Run review in the Start a review dialog starts the review right away.

Every review comment opens with its outcome and links earlier concerns that still need attention next to the new findings.

Automatic approval depends on verified behavior and unresolved concerns. When a serious risk needs more information, HeyDeer asks a question to clarify instead of approving.