Skip to main content
Replicas integrates with Linear as an assignable agent. Assign issues to Replicas like you would a team member, and it spawns a workspace to complete the task.

​
Setup

  1. Go to Integrations settings
  2. Click Connect Linear
  3. Authorize Replicas for your Linear workspace
Ensure you have at least one coding agent configured before assigning tasks.

​
How It Works

When you assign an issue to Replicas:
  1. Replicas Agent (an AI orchestrator) analyzes the issue
  2. If clarification is needed, it asks follow-up questions in a thread
  3. Once ready, it spawns a workspace with your chosen coding agent
  4. The agent works autonomously, streaming progress to the thread
  5. As work progresses, session links (workspace and PRs) appear in the Agent Session panel

​
Agent Selection

Replicas asks which coding agent to use (Claude Code or Codex) unless you’ve set a default in user preferences (click Account in the sidebar, then the Preferences tab). Org admins can also set the default agent and model for the organization.

​
Environment Selection

If your organization has multiple environments, Replicas auto-picks one from the issue context (repo names, file paths, issue title) when confident, and prompts in the agent session otherwise. The env’s binding determines what gets cloned. With a single env, or with a default environment set in Org Settings, the prompt is skipped.

​
Context

The context provided to the agent are listed below:
  • Issue title
  • Issue description (including images)
  • Parent issue content
  • Previous comments on the issue
  • User message (if triggering using @Replicas in a comment)

​
Issue State Automation

Replicas keeps the Linear issue state in sync with what the agent is doing:
  • In Progress when a workspace is created or the agent re-engages on a new comment.
  • In Review when the agent’s turn completes with a PR open.
  • Blocked when waiting on human input (env picker), a workspace fails, or a security policy denies the request.
For teams with renamed workflow states (e.g. “Code Review” instead of “In Review”), open the gear icon on the Linear card under Integrations to map each Replicas concept to a specific state per team. Unmapped slots fall back to a name-match heuristic; if nothing matches (typically for Blocked), the issue is left alone.

​
Closing the workspace

When you mark an issue as Done, Canceled, or Duplicate in Linear, Replicas automatically cleans up the associated workspace.

​
Intended Usage

Replicas works best with concise but direct instructions. Agents can typically crawl and search codebases well, so it is best to only provide a handful of sentences. Describe:
  • Where to look
  • Functionality
  • Any considerations
Add /plan in a comment to request a planning-only response with a plan link. See Plan Mode.