Setup
- Go to Organization → Integrations
- Find Linear and click Install
- Authorize Replicas for your Linear workspace
Personal Account Connection
Connect your Linear account from Personal → Connections to link your Linear user ID to your Replicas account. Replicas then uses your personal defaults and credentials even when your Linear email differs from your Replicas email. Email matching remains a fallback for members who have not connected an account. This identity connection is separate from the organization integration used by agents to create and update issues. A disconnected personal account does not mean organization access has been lost.Creating Issues from a Workspace
Ask your workspace agent to create a Linear ticket. All new workspaces keep organization credentials on the server and refresh them through the gateway; a separate Linear MCP server is not required. Usereplicas.linear.graphql() for API calls and replicas.linear.download(url) for protected attachments.
If an agent reports a rejected workspace token, ask it to retry through the gateway. Reconnect under Organization → Integrations only if the gateway reports missing credentials or an unrecoverable authentication failure. Reconnect as well if an agent cannot read initiatives; organizations connected before initiative access was added need to grant it.
Workspaces created before the gateway retain compatibility with their existing tokens, including token refresh. Agents should use the SDK when available. Customer-defined tokens remain separate from the organization integration.
How It Works
When you assign an issue to Replicas or mention it in a comment:- Replicas Agent (an AI orchestrator) analyzes the issue
- If clarification is needed, it asks follow-up questions in a thread
- Once ready, it spawns a workspace with your chosen coding agent
- The agent works autonomously, streaming progress to the thread
- As work progresses, session links (workspace and PRs) appear in the Agent Session panel
- The agent’s final response completes the Linear session
Mothership triage
Organizations with Mothership can monitor selected Linear teams from Mothership settings. Each team uses one durable Mothership chat and an instruction preset; Triage is the default for newly added teams. New issues are evaluated automatically. Using the connected Linear integration directly, Mothership either ignores the issue without writing to Linear, asks clarifying questions in a native agent session, or starts a workspace. If clarification becomes work, the workspace continues in that same Linear session. Mothership does not change labels, priority, assignee, project, or state while deciding. Existing issues are not backfilled when a team is added. When work starts, Replicas uses the issue creator’s defaults if their Linear identity maps to a Replicas member, then falls back to organization defaults. When work starts or resumes, Replicas also becomes the issue’s delegate if no agent is already delegated. The human assignee keeps ownership. Seat usage belongs to the person who starts the session, identified by their Linear email. A Replicas login is not required. If Replicas cannot identify that person, workspace creation stays blocked; start a new session by mentioning Replicas from your Linear account. If workspace provisioning or an agent turn fails, the Agent Session shows the concrete error when available and marks the issue as blocked. Readiness or initial-message delivery failures remain non-terminal so a later prompt can retry the active workspace.Agent Selection
Replicas uses the triggering user’s agent defaults when their Linear account is connected or its email matches a Replicas user. Admins can also open Linear Configure under Integrations to set Linear-specific defaults before falling back to the organization defaults. Follow-up comments wake sleeping workspaces and keep using the workspace’s selected coding agent and model. Follow-up comments also restore archived workspaces.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, a personal default, or an org default, the prompt is skipped. When the Linear user matches a Replicas user, their personal default takes precedence over the organization default.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), which scopes what the agent implements; start it with
/planfor a planning-only session
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.
Closing the workspace
When you mark an issue as Done, Canceled, or Duplicate in Linear, Replicas automatically archives the associated workspace. Archived workspaces keep their conversation history and can be explicitly restored.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
/plan to request a planning-only response with a plan link. See Plan Mode.