Your first review,
in a few minutes.
Connect GitHub
Sign in and open a workspace for your personal account or organization. The first verified organization member to create it becomes a HeyDeer admin and can manage settings and billing. Install HeyDeer or request approval from a GitHub organization owner, then select repositories. View GitHub permissions .
Pick an existing pull request
Select an open, ready-for-review PR and choose a depth. Check the minimum charge before starting. Each workspace’s 14-day trial begins after its first successful review. Waiting for installation approval does not use trial days. Existing trials keep their original deadline.
Keep the feedback coming
Set defaults in Organization settings. Use Repository settings to override individual options or restore inheritance. Draft and fork reviews are opt-in. Use @heydeer review, pause, or resume in PR comments.
Give reviewers your team’s instructions.
In Settings → Review instructions, choose Organization defaults or a repository. Add plain text or Markdown describing review priorities, conventions, and the language you want for findings. Each scope supports up to 12,000 characters.
Organization instructions apply first, followed by repository instructions. Repository preferences take precedence when they conflict. The combined preview shows both layers; saving an empty repository value restores organization-only guidance. Organization owners manage defaults, and repository admins manage repository instructions.
All reviewers receive the same instructions, including the final verification pass. Instructions are fixed when a review starts and stay the same across retries. Repository checks still run, and instructions cannot change the required result format or review safety rules. Do not put passwords or tokens in instructions.
Connect your context with MCP.
In Settings → MCP servers, choose Organization defaults or a repository, then add a server name, public HTTPS endpoint, and optional bearer token. Organization defaults apply to every repository. A repository can add servers, override a matching name, or disable an inherited server. Use organization default removes the override.
Organization owners manage defaults; repository admins manage repository connections. An override replaces the whole connection, including authentication. Tokens are encrypted and never shown again. Leave a saved token blank to keep it; when changing its endpoint, supply a replacement token or select Remove saved token.
Both reviewers use the configured Streamable HTTP servers. Use public HTTPS endpoints on port 443 without query parameters, and read-only tokens from servers you trust: MCP requests may include code or other review context. Interactive OAuth, local commands, legacy SSE-only servers, and custom tool definitions are not supported. Configuration is fixed when a review starts; edits apply to later reviews.