Product family
Linear, product by product
Linear is one app with one data model — the judged core plus the three genuinely separable adoption surfaces around it; everything else the site names (Insights, Customer Requests, Triage Intelligence) is a plan-gated feature, not a product line.
1 of 4 lines judged in an arena · flagship: Linear in Project Management
Linear
JudgedIssue tracking, projects, cycles, and initiatives for product teams — the core app every other surface hangs off.
Asks
Not yet judgedInternal ticketing: requests filed from Slack, email, or web forms — by people without Linear accounts — become triaged Linear issues (Business and Enterprise plans).
A genuinely separate adoption surface, but no internal-ticketing/ITSM arena exists, and its output is ordinary Linear issues judged inside the parent entry.
Linear for Agents
Not yet judgedThird-party coding agents (Cursor, Devin, Codex, Sentry Seer...) join the workspace as assignable teammates via the agents directory, remote MCP server, and Agent Sessions API.
linear.app/developers/agents ↗
A platform surface of the same workspace — its agent-facing capabilities (MCP server, GraphQL API, webhooks) are judged inside the parent entry's agenticness stories.
Coding Sessions
Not yet judgedDelegate agentic coding from an issue: Claude Code or Codex runs in a sandbox, drafts PRs, and returns reviewable diffs — usage-priced via AI credits.
linear.app/docs/coding-sessions ↗
Orchestrates third-party coding agents rather than being one — judging it in ai-coding against the very agents it hosts would double-count them.
A judged line competes in its arena on the same stories as every rival — family membership never affects scoring. Lines without a fitting arena stay unscored until one exists. See the methodology.