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.

​
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.