Key findings
- Linear reported in March 2026 that coding agents are installed in more than 75% of its enterprise workspaces and that agents authored nearly 25% of new issues (Linear's figures).
- In Linear's fixed group, teams with a coding agent connected went from 21 to 65 pull requests per week over two years, against 8 to 10 for teams without one. These are Linear's figures, and the two groups started at different levels.
- 51 public accounts, 30 of them from individual developers, say the issue now works as the agent's brief.
- 56 of the 138 public accounts that discuss agents and Linear report problems, from agents that loop on tokens to a delegation that returned no result.
Once coding agents pick up Linear issues, the issue is the agent's whole brief, so write the outcome, the scope, and what must not change into every issue you delegate. Route agent work by label rules, verify what agents write back, and set an AI credit limit before you automate.
What Linear's data shows
Linear's 2026 report on its customer base finds AI-feature usage grew between January and June 2026. The share of users active on those features more than doubled in every function. Pull requests opened per workspace rose 111% from a June 2024 baseline. In its fixed group, teams with a coding agent connected roughly tripled their weekly pull requests, while teams without one barely moved.
Time spent on planning inside Linear held steady over the same year, which Linear reads as AI changing how teams execute more than how they decide what to build. These are Linear's figures on its own customers, and they count pull requests opened. Linear itself notes that "an opened PR says nothing about the value of the change", so measure merged agent pull requests in your own repositories.
| Teams | June 2024 | June 2026 |
|---|---|---|
| Teams with a coding agent connected | 21 | 65 |
| Teams without one | 8 | 10 |
Linear, How teams build: AI usage patterns in software teams (2026)
The issue becomes the spec
Linear's coding-session guide contrasts an ambiguous issue with one that names the file, the flag to reuse, and what must not change. It says the clearer issue costs fewer AI credits. Teams report the same rule. Niptao's agent copies every clarifying question and answer onto the issue, so the issue holds the whole conversation. A developer running Codex with the Linear MCP server lets the planning chat write the issue. Another team pairs each issue with a short human-written prompt, which it says keeps its tickets honest.
The work shifts to before the agent starts. A product manager whose company had just moved to Linear expects scoping tickets to become the main job, after an AI automation opened four branches and closed them with no changes.
Routing and automation
Delegation moves from one-off assignment to rules. Niptao's loop works Todo issues that carry an agent label, by priority, switches to an agent-blocked label while it waits for a person, and never touches an issue labeled manual. Linear documents the same pattern for its own coding sessions through Triage automations.
Identifiers matter more to agents than to people. Linear issue numbers belong to the team, so an agent told to work one team's issues sees every project in that team. A GitHub issue on Linear's repository reports that the MCP server works one project at a time, so agents that move between projects can file issues in the wrong place.
Where it strains
Developers report friction where Linear connects to their agents and tools. One uninstalled the MCP server as unreliable and built a CLI instead. Another found Linear's API returned success for fields it ignored, so that workflow now verifies every write. A solo founder running about 40 agents finds Linear too token-heavy to use as working context, and others prefer to keep AI out of the tracker altogether.
Spend follows usage. One developer's company runs an agent on every new issue while it has free AI credits and expects to stop when they run out. Coding sessions bill tokens plus sandbox time from a pooled balance anyone with access can draw on.
- Write issues with outcome, scope, and what must not change.
- Route by rule, and fence off issues an agent must not touch.
- Verify agent writes to the tracker.
- Set a spend limit before automating.
Methodology
GILD synthesis of Linear's published report and announcement, labeled as Linear's figures, and the 138 public accounts in Linear's Signals that discuss agents, each opened on October 12, 24, or 25, 2026. Practitioner counts describe these 138 sources only.
Products in this piece
Sources
- Official documentation
- 6
- Public source
- 12
- Linear: How teams build, AI usage patterns in software teams (2026)
- Linear: Issue tracking is dead (Mar 24, 2026)
- Linear docs: Coding sessions
- Linear docs: AI agents
- Linear docs: AI credits
- Linear docs: MCP server
- Shashank Singla, Niptao: An engineer you manage from a group chat (Jun 10, 2026)
- Hacker News: Codex with the Linear MCP server writes the issue (May 26, 2026)
- Hacker News: Linear issues as agent context keep tickets honest (Apr 22, 2026)
- V_Ster on Reddit r/ProductManagement: scoping tickets after moving to Linear (Apr 8, 2026)
- GitHub issue on linear/linear: the MCP server works one project at a time (May 17, 2026)
- Hacker News: an agent on every new Linear issue, paid with free AI credits (Jul 6, 2026)
- Sketaverse on Reddit r/ProductManagement: Linear as context for 40 agents (Sep 13, 2026)
- Fernando Rodriguez on DEV: Linear Agent isn't what you need (Apr 30, 2026)
- Mike on DEV: How my AI agent keeps Linear and Jira in sync (Jul 24, 2026)
- Hacker News: specifications in Linear as agent context (Sep 21, 2026)
- Hacker News: PRD to Linear issues in a Ready for Agent status (Apr 15, 2026)
- Hacker News: keep AI away from the issue tracker (Mar 24, 2026)