Skip to main content

​
Prerequisites

  • Replicas account
  • GitHub or GitLab account with repository access
  • At least one of:
    • Claude Code subscription, Anthropic API key, or AWS Bedrock credentials
    • Codex subscription
    • Cursor API key
    • OpenRouter API key

​
Step 1: Connect GitHub & Add a Repository

Connect your GitHub account and add at least one repository for Replicas to work on.
  1. Go to the dashboard. The onboarding guide will open automatically
  2. Click Connect GitHub and authorize your account
  3. Install the Replicas GitHub App on the repositories you want to use
  4. Search and select a repository to add
Prefer GitLab? Connect GitLab under Source control instead and add GitLab projects; everything below works the same, with merge requests in place of pull requests. See GitLab integration.
You can manage repositories later in Integrations settings. When you add a repository, Replicas auto-creates a default environment bound to it; pick that environment when creating a workspace. If you work across several repositories, create a Repository Set and bind an environment to that set instead.

​
Step 2: Connect a Coding Agent

Replicas uses your own Claude Code subscription, Anthropic API key, Codex subscription, Cursor API key, or OpenRouter API key to power workspaces. You need to connect at least one.

​
Option A: Bring Your Subscription (CLI)

First, install the Replicas CLI: 
curl -fsSL https://tryreplicas.com/install.sh | bash
replicas login
Then authenticate with your coding agent: 
replicas claude-auth   # For Claude Code
replicas codex-auth    # For Codex
This opens a browser to authenticate with your existing subscription.

​
Option B: Anthropic API Key

If you prefer to use a direct Anthropic API key for Claude, enter it in the onboarding guide or in Coding Agents settings. Keys start with sk-ant-.

​
Option C: AWS Bedrock

If you prefer to use Claude via AWS Bedrock, enter your AWS credentials directly in the onboarding guide or in Coding Agents settings:
  • AWS Access Key ID
  • AWS Secret Access Key
  • AWS Region (e.g., us-east-1)

​
Option D: Cursor API Key

If you prefer Cursor, enter your Cursor API key in the onboarding guide or in Coding Agents settings. Generate a key from Cursor Dashboard → Integrations. See the Cursor agent guide and credentials for more details.

​
Option E: OpenRouter API Key

If you prefer Opencode, enter your OpenRouter API key in the onboarding guide or in Coding Agents settings. Generate a key from the OpenRouter keys page. See the Opencode agent guide and credentials for more details.
All credentials are encrypted and only accessed when provisioning workspaces.

​
Step 3: Create Your First Workspace

A workspace is an isolated environment where a coding agent works on your repository.
  1. Click New Workspace in the sidebar (or use the onboarding guide)
  2. Pick an environment (the default one Replicas created for your repository works out of the box) and give the workspace a name
  3. Start chatting with your agent
The agent can read your code, make changes, run commands, and create pull requests, all within the sandboxed workspace.

​
Optional: Enable Integrations

Supercharge your workflow by connecting integrations. These let you trigger Replicas from external sources instead of only through the dashboard.

​
Linear

Assign Linear issues directly to Replicas like you would a team member.
  1. Go to Integrations settings
  2. Click Connect Linear and authorize your workspace
  3. Assign any issue to Replicas. It will spin up a workspace and start working
Learn more about Linear integration

​
Slack

Mention @Replicas in Slack channels to start tasks conversationally.
  1. Go to Integrations settings
  2. Click Connect Slack and authorize for your workspace
  3. Invite @Replicas to channels and mention it to start a task
Learn more about Slack integration

​
GitHub Triggers

Enable @tryreplicas mentions on GitHub issues and pull requests. Once you’ve added a repository to your organization (Step 1), you can mention @tryreplicas on any GitHub issue or PR to trigger a workspace. Need always-on responses for reviewer bots? In Organization Settings → GitHub Auto Responders, search for bots like greptile-apps[bot] so Replicas reacts automatically without @tryreplicas. Learn more about GitHub integration

​
GitLab Triggers

Enable @tryreplicas mentions on GitLab issues and merge requests. Once you’ve connected GitLab and added a project, mention @tryreplicas on any GitLab issue or MR to trigger a workspace. Learn more about GitLab integration

​
Optional: Invite Team Members

Add teammates to your organization so they can create workspaces and use integrations.
  1. Go to Members settings
  2. Enter their email to send an invite
  3. They’ll receive an email to join your organization

​
Customizing Workspace Setup

Create a replicas.json or replicas.yaml file in your repository root to customize how workspaces initialize: 
{
  "startHook": {
    "commands": ["npm install", "npm run build"]
  },
  "systemPrompt": "Custom instructions for agents."
}
FieldDescription
startHookCommands to run when the workspace starts.
systemPromptCustom instructions for the coding agent.
Learn more about repository configuration

​
Where to Go Next

Workspaces

How workspaces run and manage themselves

CLI

Connect to workspaces from your terminal

Linear

Assign tasks from Linear

GitHub

Trigger from GitHub issues and PRs

GitLab

Trigger from GitLab issues and MRs