Connect Linear to your factory

Connect Linear to your factory so your team can send it issues without leaving Linear. Assign an issue to the factory or tag it in a comment, and the factory picks up the issue with its full context.

From there, the factory routes the issue through its stages, triage through review, and keeps the Linear issue updated as work progresses, so your team can follow along without switching tools. If you’re new to factories, see how Warp Factories work for the lifecycle.

When the factory needs human input, respond in Linear or open the live factory run to inspect and steer the agent directly.

Two parts work together:

• The Linear connection - Grants Warp access to your Linear workspace.
• Factory automations - Decide which Linear events start work and which agent handles them.

Prerequisites

• A factory - Create a factory with the agents, repositories, and environment needed to handle Linear work.
• A Linear workspace - Use a Linear account that can authorize the Warp app for the workspace.
• A linked Warp account (agent sessions only) - Anyone who starts a Linear agent session must link their Linear user to their Warp account. If Warp can’t identify the session creator, Linear shows an authentication prompt instead of starting work.
• Code host access - Configure repository access separately through the factory’s GitHub connection. The factory needs it to change code or create a pull request.

For workspace-level installation, reconnection, and removal steps, see the Linear integration setup guide.

Connect Linear during factory setup

When you create a factory, the setup flow includes a Connect your issue trackers step:

1. On the Linear row, click Connect.
2. Complete Linear’s OAuth flow for the workspace you want to connect. When you return, the Linear row shows as connected.
3. Under Linear team, select the Linear teams that should trigger your factory.

When setup completes, Warp creates a default automation that routes new agent sessions from the selected teams to your factory. Issue and comment events don’t start work until you add triggers for them.

Connect Linear from factory settings

If you skipped Linear during setup, connect it from the factory’s settings:

1. In your factory, open Settings and go to the Factory integrations section.
2. On the Linear row, click Connect. If the workspace hasn’t authorized Warp yet, complete Linear’s OAuth flow first.
3. Under Linear teams, select the teams that should trigger your factory, then click Enable.

Both paths end in the same state: Linear is connected to your factory, and a default automation routes agent sessions from the selected teams.

Route agent sessions

When someone mentions, assigns, or delegates the Warp app on an issue, Linear starts an agent session. The default automation created when you connected Linear routes new sessions from your selected teams to the factory, so assigning an issue or tagging the factory in a comment is enough to start work. If a session doesn’t match any automation, the Linear integration handles it with its default behavior.

Agent sessions don’t appear as a trigger in the automation editor. To change how sessions route, for example by creator or keyword, edit the agent_session_created event in the factory’s version-controlled definition. Replies in an existing session continue that run; they aren’t separate triggers.

Configure Linear triggers

Agent sessions cover explicit requests. To also start work automatically from issue and comment activity, add triggers:

1. In your factory, open Automations, then click New to create an automation or select an existing one.
2. Click Add trigger > Linear, then choose an event: Issue created, Issue labeled, Issue state changed, Issue assigned, or Comment created.
3. Select teams and labels to filter on. Click More filters to also filter by project, workflow state, assignee, mentioned user, or, for comment events, a specific issue.
4. Choose the agent that receives the work, add any instructions, and save.

Filters control when a trigger fires. An empty filter matches everything in the connected workspace, and every filter you add must match. For example, a trigger can require that an issue belongs to one team, enters a selected workflow state, and carries a release label.

If Linear shows Not connected in the Add trigger menu, selecting it opens the factory’s settings so you can connect Linear first.

Caution

Team selections and filters only route events. They don’t reduce what the connection is allowed to access; the OAuth flow sets the workspace and teams Warp can reach.

Supported events and outputs

Each event determines the context the agent receives and the updates the factory sends back.

Linear event	What the agent receives	What the factory sends back
Issue created, labeled, state changed, or assigned	The issue’s title, description, team, project, labels, workflow state, and assignee	Work item progress, issue state or delegate changes, and links to results
Comment created	The new comment and its issue’s context	An acknowledgment, progress updates, and responses
Agent session created	The request that mentioned, assigned, or delegated the Warp app	Live progress in the session, plus links to the run and any pull request
Reply in an agent session	The new message and the session history	Continued work in the same session, not a separate work item

Follow-up events on the same issue

Once a Linear issue is linked to a factory work item, later matching events on that issue continue the same work item instead of creating a new one.

Caution

One comment can match two routes: a comment that creates an agent session can also match a Comment created trigger. If both point at your factory, a single action starts two runs. Scope your automations so one path owns each kind of request.

What the factory can do in Linear

In an agent session, the factory posts its plan, actions, and results as it works. It can also attach a GitHub pull request to the issue, update the issue’s workflow state or delegate, link back to the run, and acknowledge comments it acts on.

The factory’s own Linear activity never triggers automations, so its updates can’t start a loop of new runs.

Only agent sessions require a linked Warp account. Issue and comment events from unlinked users still start work, but Warp may not record who requested it.

The Linear connection doesn’t grant repository access or merge permissions. Code-host credentials control branches and pull requests, and human review and merge requirements still come from your factory workflow and repository settings.

Troubleshooting

• An agent session shows an authentication prompt - Complete the prompt to link your Linear user to your Warp account, then retry the request.
• Teams or filters don’t load - Reconnect Linear by following the Linear integration setup guide, then confirm the connection can access the workspace and team you expect.
• An event doesn’t start work - Confirm the automation is enabled, the event type matches, and every filter matches the issue’s current values or the state change.
• One action starts multiple runs - Look for overlapping agent-session and comment triggers, then narrow or remove one.
• No pull request appears - Check the factory’s code-host credentials and repository access. Linear authorization alone doesn’t allow code changes.