Skip to main content
Replicas responds to GitHub issue comments and PR comments. Whether starting new work from a GitHub issue, iterating on a PR from Linear, or working on any existing PR, it maintains context across all interactions.

​
Setup

  1. Go to Integrations settings
  2. Click Connect GitHub and authorize your account
  3. Install the Replicas GitHub App on your repositories
  4. Add repositories you want Replicas to access
That’s it! Once a repository is added to your organization, you can use @tryreplicas mentions on any issue or PR in that repository.
Each repository can only be connected to one Replicas organization. If you need to transfer a repository to a different organization, remove it from the current organization first.

​
How It Works

​
Trigger from GitHub Issues

Add @tryreplicas to any comment on a GitHub issue to start a new task.
  • Replicas creates a new workspace to work on the issue
  • The agent provides an implementation plan before making changes
  • When complete, the agent creates a PR and comments on the original issue with:
    • A link to the PR
    • A summary of the changes made
  • When the issue is closed, the associated workspace is automatically cleaned up
Each issue is linked to one workspace. All interactions on the issue route to the same workspace.

​
Trigger from Pull Requests

Add @tryreplicas to any pull request review (e.g requesting changes) or comment.
  • If the pull request was made by a Replicas agent, it will see it, make changes, and respond directly to you.
  • If the pull request was made by someone else, a new workspace and Replicas agent will be spun up.
Each PR is linked to one workspace. All interactions route to the same workspace, so the agent remembers previous work. If the workspace is sleeping, it wakes automatically.

​
Auto Respond To Review Bots

You can configure an allowlist in Organization Settings → GitHub Auto Responders to automatically react to specific GitHub users or bots without requiring @tryreplicas. This is useful for reviewer bots like greptile-apps[bot] and coderabbitai[bot].

​
CI/CD Failure Auto-Response

When a CI/CD check fails on a pull request linked to a Replicas workspace, the agent is automatically notified and investigates the failure. It reads the failure logs, diagnoses the issue, pushes a fix, and comments on the PR. This works with two sources of CI failures:
  • GitHub Actions workflows, triggered via workflow_run events when a workflow completes with a failure.
  • External CI checks, triggered via check_run events from any non-Actions provider that posts results through the GitHub Checks API (e.g. Mintlify, CircleCI, Buildkite).
Both sources can be independently toggled in Organization Settings → CI Failure Response:
  • Respond to CI workflows: controls auto-response for GitHub Actions failures (enabled by default).
  • Respond to CI checks: controls auto-response for external CI check failures (enabled by default).
CI providers that report status via the Statuses API or Deployments API (e.g. Vercel deployment status) are not yet covered by this feature.

​
PR Attribution

Pull requests created by Replicas agents can be attributed to you instead of the Replicas bot. This requires your GitHub account to be connected in User Settings → Connections. When enabled, the gh CLI inside the workspace uses your personal GitHub OAuth token, so gh pr create shows you as the PR author. Git operations (push/pull) still use the Replicas app token. This feature is off by default and can be controlled at three levels:
  • User preference (pr_user_attribution): Toggle in Account Settings → Preferences to attribute PRs to you for your own workspaces.
  • Organization preference (pr_user_attribution): Toggle in Organization Settings → PR Attribution to set the org-wide default.
  • Organization security policy (require_pr_user_attribution): Toggle in Organization Settings → Security Policies. When enabled, all workspaces in the org attribute PRs to the user regardless of individual user preferences.
If you haven’t connected your GitHub account, PRs will be attributed to the Replicas bot regardless of these settings.

​
Context

For issues, the context includes:
  • Issue number, title, and description
  • Your comment body
For pull requests, the context includes:
  • PR number and branch
  • Your comment or review body
  • Review state (approved, changes requested, etc.)
  • File path and diff hunk (for line comments)

​
Intended Usage

Use GitHub Issues to:
  • Start new features or bug fixes directly from issue tracking
  • Get implementation plans before code changes
  • Track work from issue to PR automatically
Use GitHub PRs to:
  • Request changes on PRs
  • Comment on specific lines
  • Ask for fixes or improvements
Add /plan in your comment to request a planning-only response with a plan link. See Plan Mode.