Story
AI usage patterns in software teams
1 report
1 website
1 discussion
Latest report
Overview
Linear’s aggregated data from paid workspaces shows AI use spreading across software-team functions and correlating with higher software-development activity through 2026. From January to June 2026, the share of users active on Linear AI features more than doubled in every measured function: product rose from 12% to 34%, engineering from 12% to 30%, design from 6% to 22%, and go-to-market from 5% to 18%. Adoption was similar across company sizes, while CEOs at companies with 201 or more employees increased from 9% to 36%. These figures cover AI interactions inside Linear, including in-app and Slack conversations and agent sessions, rather than all AI use. AI agents and MCP created 2.435 million Linear issues in the week of August 3, 2026, compared with 2.481 million created by people and integrations. Pull requests opened per workspace were 111% above the June 2024 baseline by June 2026. In a fixed cohort, workspaces connected to coding agents rose from 21 to 65 pull requests per team per week over two years, while teams without a connected agent rose from 8 to 10. The share of product users attaching pull requests increased from 3% in June 2024 to 10% in June 2026, and designers rose from 1% to 8%. Linear found that time spent on existing coordination work generally increased or held steady, while AI chat and agent work added new activity; it does not measure whether the added output produced positive business outcomes.
Summary from linear.app.
Reports
One report so far. Additional coverage will appear here when it is linked to this story.
Community reactions
Each reaction summarizes sampled comments from the linked discussion.
Hacker News · linear.app
Historical count: 7 · 7 saved in sample · Historical sample
Analysis ready
Read this discussion’s reaction
Based on 7 sampled comments from this thread. Analyzed 2026-08-19.
The thread mostly rejected the article’s dashboard as a measure of whether AI is making software teams better. Commenters accepted that AI is visibly changing execution: code can be generated quickly, and teams are experimenting with guarded pipelines that push routine implementation and review work toward automation. One reader even framed rapid generation-and-commit workflows as an enormous productivity gain when the output is already sound. But the prevailing view was that PR counts, issue activity, token consumption, and time spent in a project tracker are cheap proxies for the hard question: did the team ship a better product, respond to customers faster, or make wiser decisions? Several readers stressed that much AI use happens outside Linear, in coding assistants, research tools, and desktop chatbots, so the data cannot support broad claims about how AI affects planning. Others noted attribution is shaky even within the platform: an AI interaction near a PR does not establish that AI produced the change. Suggested alternatives included operational measures such as incident detection and recovery, approval rates, spending, and workflow focus, ideally tied to customer satisfaction. Privacy also emerged as a separate objection, with one camp treating aggregated publication as harmless and another seeing intimate usage telemetry as an unacceptable bargain.
The sharpest fight is whether activity telemetry can show AI’s real value to software teams. Defenders see aggregate usage and newer operational metrics as a practical early signal of changing workflows, while critics argue that tracker-visible output is incomplete, weakly attributable, and potentially inversely related to customer value.
- Praise: Fast code generation can dramatically compress implementation time when developers can trust the result enough to commit without an extended repair cycle.
- Praise: AI-driven code pipelines with guardrails are seen as a route to stripping unnecessary review latency from routine engineering work.
- Praise: Richer AI workflow signals such as approval rates, incident recovery, budgets, and focus patterns could move measurement beyond raw token and pull-request counts.
- Concern: Generating code faster can merely shift the burden into long reading, cleanup, and repeated prompting sessions, leaving total delivery time worse rather than better.
- Concern: Pull requests, issues, and tracker activity measure visible churn, not whether AI improved product decisions, customer outcomes, or software quality.
- Concern: Most meaningful AI assistance occurs in coding and research tools outside the tracker, so platform telemetry misses both planning influence and a large share of implementation work.
- Concern: Linking an AI interaction to a nearby pull request is correlation masquerading as attribution, especially when repository tracking adoption itself is changing.
- Concern: Publishing aggregated AI-usage statistics still alarms privacy-minded teams that do not want a work platform collecting intimate behavioral telemetry.