Linear: AI Authorship Hits 48% in Dev Teams—Execution Soars, Planning Stalls

LONDON, Friday, August 21, 2026 —

According to Linear's public data statement, teams now use AI to write just under half of everything created in Linear, and at the current pace it could soon author more than people and integrations combined. Linear, used by over 25,000 companies, published the data on its official data dashboard, marking the most concrete signal yet of AI adoption penetration in enterprise software development workflows.

The milestone arrives at a critical inflection point in software engineering velocity. According to Linear's public data, two years ago, fewer than one issue in a thousand was created by AI. The acceleration to 48% reflects rapid adoption of Linear Agent, the platform's native AI tool launched in March 2026, which can create issues from Slack messages, auto-triage bugs, and route work to team members based on historical patterns. Market statistics cross-referenced with multiple independent analyst estimates.

However, the data reveals a critical divergence: execution speed has moved dramatically, but planning discipline has not. Time spent on customer requests, docs, and projects held steady in a year when nearly everything else in this report moved up. What the steadiness suggests is that AI has so far changed how teams execute far more than how they decide what to build.

Context: AI Authorship Across the Stack

Linear's data arrives alongside parallel signals of AI penetration across software workflows. According to a Pew Research study released August 20, signs of AI authorship were found in over one-third (35%) of web pages published after the release of ChatGPT. URLs with a .com domain showed signs of AI authorship at around 10x the rate of a .edu or .gov domain (both of which were around 1% AI authored). This suggests that commercial software development teams are leading broader adoption trends.

Related: Bumble Introduces AI Dating Assistant ‘Bee,’ Signals AI Push in 2026

Vector	AI Authorship Rate	Timeline	Context
Linear Issues Created	48%	August 2026	Up from <0.1% in 2024
Post-ChatGPT Web Pages	35%	August 2026	.com domains: ~10%; .edu/.gov: ~1%
GitHub Issues (implied)	TBD	Q3 2026	Major labs expected to release data

The Linear data carries particular weight because it represents actuals, not projections. The report uses aggregated product data from Linear, including AI conversations, agent sessions, issue activity, comments, and pull requests.

Competitive Landscape: Developer Tools Reset

Linear Agent launched in March 2026 as an AI feature that creates issues from Slack messages, auto-triages bugs, suggests duplicate issues, and helps draft issue descriptions. The adoption curve suggests strong product-market fit among engineering teams migrating from legacy tools. CEO and co-founder Karri Saarinen declared that "issue tracking is dead," arguing that agents "make software development a lot simpler" as they do more of the procedural work.

For deeper context, see our AI analysis: "Meta launches Business AI in India: 91% Messaging Reach Reshapes SMB".

Competitors face immediate pressure. Atlassian's Jira continues to dominate installed base but struggles with adoption; Asana and Monday.com remain generalist platforms lacking software-specific AI. GitHub's native issue tracking, while integrated with code, has not yet matched Linear Agent's capabilities or user experience design.

Platform	AI Agent Launch	Focus Model	Adoption Driver
Linear	March 2026	Software-native AI	Slack integration, auto-triage
Jira	Q2 2026 (limited)	Atlassian Intelligence	Legacy install base
GitHub	Copilot (code-only)	Coding AI	Bundled with IDE
Asana	Asana AI (non-native)	Cross-functional	Enterprise contracts

The divergence between execution speed and planning discipline creates an opening for product leaders. Teams closing issues faster but not improving roadmap clarity face a coordination gap.

Additional coverage: Qualcomm Bets on Stellantis Partnership to Bolster Automotive AI

Why It Matters

For Enterprise Buyers

The 48% AI authorship rate signals that dev teams are not waiting for permission to adopt AI agents. Organizations procuring Linear, GitHub, or competing platforms must now budget for AI seat licenses and account for agent-created work in velocity calculations. The planning-vs-execution divergence suggests that procurement teams should pair issue tracking platform upgrades with roadmap and product management tools to prevent misalignment.

For Investors

Linear's data validates a critical thesis: developer tools are the fastest-adopting category for AI agents because they reduce friction on high-frequency tasks. The platform's position as a category leader in a 25,000+ company install base positions it for both M&A interest and high-revenue potential. Competitors without native AI agent capabilities face a widening moat.

Related: Qwen3.8-Max: Alibaba's 2.4-Trillion-Parameter Model Builds Self-Evolving Code, Reproduces Research Papers, and Beats 87% of Human Teams in Competition

What This Means for Practitioners

The Linear data forces a reckoning for engineering leaders: Linear's data suggests AI has approached the 50% threshold in issue authorship within their platform, which may affect velocity metric comparisons to historical baselines. Issues created by agents close differently, have different context depth, and often lack the nuance of human-authored tickets. Teams must reclassify metrics—separating agent-driven work from human-initiated work—to maintain fidelity in sprint planning and retrospectives. The finding that planning velocity has not improved suggests that your planning ceremonies may be the new bottleneck, not execution capacity.

What Happens Next

Linear is expected to release expanded agent capabilities by Q4 2026, including deeper GitHub integration and multi-repository issue synthesis. GitHub and Atlassian are racing to match Linear Agent's adoption curves. In parallel, enterprise software procurement teams will face pressure from engineering leaders to standardize on AI-native platforms, driving potential consolidation among legacy tool vendors. The question for CIOs is no longer whether to adopt AI agents in dev workflows, but which platform's agent architecture will become the standard.

For deeper context, see our Genomics analysis: "Beyond the Sequencer: What Genomics ROI Actually Looks Like in 2026".

FAQ

Q: Does the 48% figure mean AI writes better issues than humans?
A: Not necessarily. Linear's data measures authorship source, not quality. Linear Agent creates issues faster and with less context-switching, but human-authored issues often contain richer business context. The 48% represents volume, not quality benchmarking.

Q: How does this compare to other development tools?
A: Linear leads in AI agent adoption among issue trackers. GitHub Copilot focuses on code, not issue creation. Jira's AI capabilities rolled out later and target existing Atlassian install bases. Linear's greenfield adoption advantage is substantial.

Q: Will this AI authorship rate continue to accelerate?
A: Linear projects it will, given current velocity. However, platform saturation effects, improved human-AI triage processes, and regulatory concerns around AI-generated work could moderate growth by 2027.

Q: What should teams do about agent-authored issues in retrospectives?
A: Separate AI-created work from human-initiated work in velocity calculations. Adjust burndown charts to account for higher agent throughput but lower context depth per issue. Reclassify "done" criteria to reflect agent-created work's different validation requirements.

Sources include company disclosures, regulatory filings, analyst reports, and industry briefings.

Related Coverage

• More AI Analysis
• Latest Technology News

Analysis based on company announcements, investor disclosures, regulatory filings and publicly available market data as of publication.