Linear is launching coding sessions, a feature that lets its built-in agent take a triage issue, investigate the root cause in the codebase, write the fix, open a pull request, and bring the diff back for human review without leaving Linear. The release bundles three things: agent-run coding sessions, team-level triage automation that routes incoming bug reports and alerts to the agent when confidence in the root cause is high, and pull request diffs viewable and commentable directly inside Linear. It is aimed at engineering and design teams already using Linear as a project and issue tracking platform who want unplanned work, small bugs, copy changes, and UI tweaks handled before a human engineer picks them up.
The launch matters because most agent coding today happens in isolated chat windows or separate sandboxes, disconnected from the issue, the reviewer, and the team. Linear is trying to put the agent, the PR, and the discussion in the same surface where product work already lives, which the company demonstrates internally by having the agent resolve a meaningful share of its own triage queue and ship PRs alongside human reviewers. For designers, the pitch is being able to delegate small visual fixes from inside the product context that prompted the question, and for engineers it is a cleaner handoff when the agent cannot close an issue on its own.
Linear was founded by Karri Saarinen, Tuomas Artman, and Jori Lallo, all Finnish but now based in the Bay Area , with Saarinen as CEO, Lallo as CPO, and Artman as CTO . The company started as an issue-tracking tool helping developers coordinate on eliminating blockers and fixing problems, but has expanded into a product-development system , and this release continues that arc by treating agents as first-class collaborators inside the same workflow as the humans on the team.
Comments (14)
Sign in to join the discussion.
R
Renata K.Jun 11, 2026
The cut from triage to PR in the video is suspiciously smooth. Either your editor is a magician or that demo has been rehearsed more times than a Broadway show.
A
Amara O.Jun 11, 2026
The pacing in that video is genuinely tight. Whoever decided to mute the typing sfx and let the cursor do the talking deserves a raise.
O
Obafemi A.Jun 11, 2026
Cool, so now my agent and I can both miss the same deadline together. Real teamwork.
M
Miranda ParkJun 11, 2026
Tagline could lose 'system' and breathe a little. 'Where teams and agents ship together' does the same work in fewer syllables.
V
Vikram P.Jun 11, 2026
Genuinely curious how the agent handles a vague issue like 'login feels weird sometimes'. That's where my real backlog lives.
T
Tomasz B.Jun 11, 2026
Staff eng question: what happens when two agents pick up overlapping issues and open conflicting PRs? Asking because I know my team will absolutely cause this on day one.
N
Nour EldinJun 11, 2026
What's the actual merge rate on agent PRs in real customer workspaces? Opening a PR is easy, getting it accepted is the interesting metric.
J
Jonas F.Jun 11, 2026
Off the record or on, any plans to open the agent protocol so other tools can plug in? Feels like the obvious next beat.
S
soyeonJun 11, 2026
The launch tweet leading with a noun phrase instead of a verb is a choice. 'Linear Agent now ships your PRs' would have done numbers.
D
Dana BettencourtJun 11, 2026
Three weeks out from my own launch and now I'm wondering if I should just let an agent finish it for me. This is psychological warfare.
H
Hiro M.Jun 11, 2026
One more thing for the roadmap: let the agent write the changelog too, because nobody on my team will.
L
Lukas V.Jun 11, 2026
Distribution question: how does this surface for teams that live in Slack? Half my standups happen in threads I'll never read again.
P
Priya R.Jun 11, 2026
First impression of the onboarding for agent setup is honestly clean. The 'assign to Linear Agent' affordance feels like it's been there forever, which is the highest compliment.
C
Celeste ByrneJun 11, 2026
Interesting. Would like to see retention on agent-authored PRs six months in before I get excited about the category.
Work With Us
Book an intro call to explore our suite of services. We might have a waitlist.
Linear
The product development system for teams and agents
The product development system for teams and agents
Tags
TLVC Rating
Community Rating
No ratings yet
to rate this launch.
Linear is launching coding sessions, a feature that lets its built-in agent take a triage issue, investigate the root cause in the codebase, write the fix, open a pull request, and bring the diff back for human review without leaving Linear. The release bundles three things: agent-run coding sessions, team-level triage automation that routes incoming bug reports and alerts to the agent when confidence in the root cause is high, and pull request diffs viewable and commentable directly inside Linear. It is aimed at engineering and design teams already using Linear as a project and issue tracking platform who want unplanned work, small bugs, copy changes, and UI tweaks handled before a human engineer picks them up. The launch matters because most agent coding today happens in isolated chat windows or separate sandboxes, disconnected from the issue, the reviewer, and the team. Linear is trying to put the agent, the PR, and the discussion in the same surface where product work already lives, which the company demonstrates internally by having the agent resolve a meaningful share of its own triage queue and ship PRs alongside human reviewers. For designers, the pitch is being able to delegate small visual fixes from inside the product context that prompted the question, and for engineers it is a cleaner handoff when the agent cannot close an issue on its own. Linear was founded by Karri Saarinen, Tuomas Artman, and Jori Lallo, all Finnish but now based in the Bay Area , with Saarinen as CEO, Lallo as CPO, and Artman as CTO . The company started as an issue-tracking tool helping developers coordinate on eliminating blockers and fixing problems, but has expanded into a product-development system , and this release continues that arc by treating agents as first-class collaborators inside the same workflow as the humans on the team.
Comments (14)
The cut from triage to PR in the video is suspiciously smooth. Either your editor is a magician or that demo has been rehearsed more times than a Broadway show.
The pacing in that video is genuinely tight. Whoever decided to mute the typing sfx and let the cursor do the talking deserves a raise.
Cool, so now my agent and I can both miss the same deadline together. Real teamwork.
Tagline could lose 'system' and breathe a little. 'Where teams and agents ship together' does the same work in fewer syllables.
Genuinely curious how the agent handles a vague issue like 'login feels weird sometimes'. That's where my real backlog lives.
Staff eng question: what happens when two agents pick up overlapping issues and open conflicting PRs? Asking because I know my team will absolutely cause this on day one.
What's the actual merge rate on agent PRs in real customer workspaces? Opening a PR is easy, getting it accepted is the interesting metric.
Off the record or on, any plans to open the agent protocol so other tools can plug in? Feels like the obvious next beat.
The launch tweet leading with a noun phrase instead of a verb is a choice. 'Linear Agent now ships your PRs' would have done numbers.
Three weeks out from my own launch and now I'm wondering if I should just let an agent finish it for me. This is psychological warfare.
One more thing for the roadmap: let the agent write the changelog too, because nobody on my team will.
Distribution question: how does this surface for teams that live in Slack? Half my standups happen in threads I'll never read again.
First impression of the onboarding for agent setup is honestly clean. The 'assign to Linear Agent' affordance feels like it's been there forever, which is the highest compliment.
Interesting. Would like to see retention on agent-authored PRs six months in before I get excited about the category.