Linear vs Notion
free-tier · subscription-per-seat · enterprise-custom · credits
·free-tier · subscription-per-seat · enterprise-custom · credits
Linear wins · 31–14 (30 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to NotionLinear's developer docs are exposed as clean .md pages (agents.md, graphql.md, webhooks.md, sdk.md, aig.md), a pattern consistent with agent-oriented/llms.txt-style documentation that an AI agent could be pointed at directly. However, there's no explicit llms.txt file cited, no first-party statement framing these docs as agent-consumption-optimized, and no independent evidence of an agent successfully using them this way. Missing for 10: explicit llms.txt manifest, documentation of agent-readability intent, third-party confirmation of successful agent consumption.
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
- [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
- [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
- [claimed-docs] “The agent must signal its identity clearly so that it can never be mistaken for a person.”
Notion's developer docs site directly serves an llms.txt file (confirmed via live probe returning HTTP 200 with structured markdown links to docs), plus a full OpenAPI spec and agent-oriented MCP guides, meaning an AI agent can be pointed at these agent-native resources to discover and use Notion's API. Missing for 10: independent third-party corroboration that agents actually consume this llms.txt successfully in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.notion.com/llms.txt # Notion Docs - [Overview](https://developers.notion.com/guides/get-star…”
- [probe] “PROBE openapi: HTTP 200 at https://developers.notion.com/openapi.json — contains "openapi" key”
- [claimed-docs] “Notion MCP lets an MCP client, such as Claude Code, Cursor, or Codex, connect to your Notion workspace through the Model Context Protocol (M…”
- [claimed-docs] “If you need to run your own MCP server, the notion-mcp-server package is available as an open-source implementation.”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to NotionLinear exposes a full GraphQL API with API-key and OAuth2 authentication, a typed SDK, webhooks for event-driven automation, and documented rate limits/deprecation policy — all of which allow scripting issue creation, queries, and workflow automation entirely headlessly (e.g. from CI pipelines) without the UI. Missing for 10: no dedicated CLI tool or explicit CI/GitHub Actions integration guide, and no independent hands-on report of using the API in a CI pipeline.
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”
- [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
- [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”
- [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
- [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
- [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
- [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
- [claimed-docs] “const myIssues = await me.assignedIssues();”
Notion's REST API plus personal access tokens explicitly target 'scripts, CLI workflows, Workers, and tools' and internal connections use static API tokens 'ideal for custom automations and workflows,' which directly supports headless/CI usage; an OpenAPI spec and llms.txt further confirm programmatic access. Missing for 10: an explicit CI/CD pipeline example or independent hands-on report of running Notion API calls in a CI environment.
- [claimed-docs] “Personal access tokens (PATs) are user-scoped tokens for scripts, CLI workflows, Workers, and tools that should act as one Notion user.”
- [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
- [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
- [probe] “PROBE openapi: HTTP 200 at https://developers.notion.com/openapi.json — contains "openapi" key”
- [claimed-docs] “create a personal access token, make your first API request, and see a new page appear in your workspace in under two minutes”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · round drawnLinearnone0/10All MCP-related evidence (linear-probe-1, linear-docs-67, linear-intdir-4, linear-intdir-6) describes Linear exposing its OWN MCP server so that other tools (Cursor, Claude) can connect TO Linear — the opposite direction from the story, which asks whether a user can plug external MCP servers INTO Linear so Linear's agent can use their tools. No evidence shows Linear or Linear Agent consuming/importing third-party MCP servers as a client.
- [probe] “official MCP server documented at https://linear.app/docs/mcp”
- [claimed-docs] “Linear's MCP now supports managing employee access through your existing Okta-managed identity.”
- [claimed-docs] “Connect Cursor to the Linear MCP server”
- [claimed-docs] “Connect Claude to the Linear MCP server”
Notionnone0/10All MCP evidence describes Notion exposing an MCP *server* so external clients (Claude Code, Cursor, Codex) can pull Notion's tools in — the opposite direction of the story, which asks whether Notion itself can plug in external MCP servers to use their tools. No evidence shows Notion's AI/agent features consuming third-party MCP servers as a client.
- [claimed-docs] “Build an MCP client that connects to Notion MCP using OAuth 2.0 with PKCE.”
- [claimed-docs] “Notion MCP lets an MCP client, such as Claude Code, Cursor, or Codex, connect to your Notion workspace through the Model Context Protocol (M…”
- [claimed-docs] “If you need to run your own MCP server, the notion-mcp-server package is available as an open-source implementation.”
- [claimed-docs] “Workspace owners can manage MCP client access in Settings → Connections.”
ai-native userConnect an agent via an official MCP server
weight 3 · round to NotionLinear publishes an official MCP server (docs page at linear.app/docs/mcp) and the changelog confirms ongoing feature work on it (e.g., Okta-based access management via Linear's MCP), showing agents can connect through this official channel. Missing for 10: independent/hands-on verification of the MCP server in use and detailed docs on setup/tool coverage beyond the single probe reference.
- [probe] “official MCP server documented at https://linear.app/docs/mcp”
- [claimed-docs] “Linear's MCP now supports managing employee access through your existing Okta-managed identity.”
Notion documents an official MCP server ('Notion MCP') that agents like Claude Code, Cursor, or Codex can connect to via OAuth 2.0/PKCE, with docs on client setup, security best practices, and workspace admin controls for MCP access. missing for 10: independent/hands-on third-party verification of the MCP server's reliability in production use.
- [claimed-docs] “Notion MCP lets an MCP client, such as Claude Code, Cursor, or Codex, connect to your Notion workspace through the Model Context Protocol (M…”
- [claimed-docs] “Build an MCP client that connects to Notion MCP using OAuth 2.0 with PKCE.”
- [claimed-docs] “Search content in Notion and connected sources. * Read, create, and update Notion content. * Create pages and databases.”
- [claimed-docs] “Enable confirmation before actions that change content. This lets you review an action before the MCP client runs it.”
- [claimed-docs] “Workspace owners can manage MCP client access in Settings → Connections.”
- [probe] “official MCP server documented at https://developers.notion.com/docs/mcp”
ai-native userUse an official CLI
weight 2 · round drawnLinearnone0/10The evidence pack documents Linear's GraphQL API, TypeScript SDK, webhooks, OAuth, and MCP server, but nowhere mentions an official command-line interface (CLI) tool for interacting with Linear. Since CLI is a plausible and common tool for developer-facing products, its absence here is a gap rather than an inapplicable axis.
Notionnone0/10Evidence shows REST API, PATs, MCP server/client support, and webhooks, but no mention anywhere of an official command-line interface (CLI) tool shipped by Notion; PATs are described as usable 'for scripts, CLI workflows' but that refers to third-party/custom CLIs built by developers, not an official Notion CLI.
- [claimed-docs] “Personal access tokens (PATs) are user-scoped tokens for scripts, CLI workflows, Workers, and tools that should act as one Notion user.”
- [claimed-docs] “create a personal access token, make your first API request, and see a new page appear in your workspace in under two minutes”
ai-native userDrive the product through a documented public API
weight 3 · round drawnLinear ships a well-documented public GraphQL API with introspection, an explorable schema via Apollo Studio, OAuth2/API-key auth, TypeScript SDK, webhooks, rate-limit documentation, and a deprecation policy, giving AI-native users a robust way to programmatically drive the product. missing for 10: independent hands-on developer reports validating real-world API usage/reliability beyond Linear's own docs.
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”
- [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
- [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
- [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”
- [claimed-docs] “query Issue { issue(id: "BLA-123") { id title description } }”
- [claimed-docs] “const myIssues = await me.assignedIssues();”
- [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
- [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
- [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
- [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
- [claimed-docs] “Docs, "Deprecations": "Linear's GraphQL API doesn't have versioning like many REST APIs... we take breaking changes and deprecations serious…”
Notion ships a well-documented public REST API with OpenAPI spec, PATs/OAuth for internal and public connections, webhooks, and even dedicated Agent APIs and MCP guides for AI-native workflows, confirmed by live probes (openapi.json, llms.txt). missing for 10: independent third-party hands-on developer reports validating real-world API robustness beyond vendor docs.
- [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
- [claimed-docs] “Personal access tokens (PATs) are user-scoped tokens for scripts, CLI workflows, Workers, and tools that should act as one Notion user.”
- [claimed-docs] “Public connections use OAuth 2.0 for authentication... Public connections must undergo a Notion security review before being listed on the M…”
- [claimed-docs] “create a personal access token, make your first API request, and see a new page appear in your workspace in under two minutes”
- [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
- [claimed-docs] “Search content in Notion and connected sources. * Read, create, and update Notion content. * Create pages and databases.”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.notion.com/llms.txt # Notion Docs - [Overview](https://developers.notion.com/guides/get-star…”
- [probe] “PROBE openapi: HTTP 200 at https://developers.notion.com/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://developers.notion.com/docs/mcp”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to NotionLinear documents OAuth2 apps with distinct scopes (e.g. app:assignable, app:mentionable) for building agents, admin approval workflows for third-party apps, and per-key rate limits differentiated by auth type, which together enable a degree of least-privilege credentialing for agent integrations. However, personal API keys (the simpler credential path) are not shown to be scope-limited, and there's no first-party or independent evidence of fine-grained per-resource/action scoping akin to full least-privilege IAM. Missing for 10: documentation of scoped personal API keys, granular resource-level permission control beyond the small named scope list, and independent/hands-on verification of least-privilege enforcement.
- [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”
- [claimed-docs] “app:assignable | Allow the app to be assigned as a delegate on issues and made a member of projects app:mentionable | Allow the app to be me…”
- [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
- [claimed-docs] “Third-party app approvals are now available on paid Linear plans, allowing admins to review and approve apps before they're installed.”
- [claimed-docs] “Use URL parameters to send users directly to a pre-filled Create OAuth App form in Linear. An equivalent JSON manifest format lets you store…”
- [claimed-docs] “Admins can manage access centrally, without requiring employees to sign in or authorize Linear individually.”
- [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
Notion documents multiple credential-scoping mechanisms relevant to agents: internal connections use a static token scoped to a single workspace, public/OAuth connections let you choose an installation scope, Custom Agent connections only reach agents explicitly shared with them, and MCP security best practices let owners require confirmation before write actions and manage client access per workspace. This shows real least-privilege controls but not fine-grained (e.g. per-resource read/write, expiring/rotatable) scopes explicitly documented. Missing for 10: documented granular permission types (read-only vs write vs admin) for API tokens, token expiration/rotation policy, and independent/hands-on confirmation that scoping works as described in practice.
- [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
- [claimed-docs] “Public connections use OAuth 2.0 for authentication. At creation time, you choose their installation scope”
- [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token.”
- [claimed-docs] “Enable confirmation before actions that change content. This lets you review an action before the MCP client runs it.”
- [claimed-docs] “The connection can access only Custom Agents that are explicitly shared with it.”
- [claimed-docs] “Workspace owners can manage MCP client access in Settings → Connections.”
ai-native userBuild against official SDKs
weight 2 · round drawnLinear publishes an official TypeScript SDK exposing its GraphQL schema with strongly typed models (linear-docs-53, linear-docs-89, linear-docs-93), backed by full GraphQL API docs, introspection, published schema SDL, OAuth2/API key auth, rate limits, and deprecation policy (linear-supp-graphql-introspection, linear-supp-apollo-explorer, linear-supp-rate-limits, linear-supp-deprecations, linear-docs-99, linear-docs-50). This gives AI-native developers a solid, well-documented official SDK to build against. Missing for 10: independent/hands-on developer corroboration (e.g., GitHub stars, community usage reports) of the SDK itself beyond official docs, and SDKs in languages beyond TypeScript.
- [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
- [claimed-docs] “Install the Linear SDK to use strongly typed models and operations”
- [claimed-docs] “const myIssues = await me.assignedIssues();”
- [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
- [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
- [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
- [claimed-docs] “Docs, "Deprecations": "Linear's GraphQL API doesn't have versioning like many REST APIs... we take breaking changes and deprecations serious…”
- [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
- [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”
Notion publishes a full REST API with OpenAPI spec, official SDK-style access via internal/public connections and PATs, an official MCP server/client guides, webhooks, and Agent APIs with SDK-like session/streaming semantics — all documented first-party and confirmed by live probes (openapi.json, llms.txt, MCP docs). Missing for 10: independent hands-on developer corroboration of SDK usage and no explicit mention of language-specific official SDK libraries (only REST/OpenAPI + MCP tooling), so some ambiguity remains on 'official SDK' vs REST/OpenAPI wrapper.
- [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
- [claimed-docs] “Personal access tokens (PATs) are user-scoped tokens for scripts, CLI workflows, Workers, and tools that should act as one Notion user.”
- [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
- [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
- [claimed-docs] “If you need to run your own MCP server, the notion-mcp-server package is available as an open-source implementation.”
- [claimed-docs] “Notion MCP lets an MCP client, such as Claude Code, Cursor, or Codex, connect to your Notion workspace through the Model Context Protocol (M…”
- [probe] “PROBE openapi: HTTP 200 at https://developers.notion.com/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://developers.notion.com/docs/mcp”
ai-native userSubscribe to events via webhooks
weight 2 · round to LinearLinear provides documented webhooks with a webhookCreate mutation to subscribe to HTTP push notifications for data create/update/delete events, plus in-app event subscriptions for project views routed to Inbox/Slack, giving AI-native users clear ways to consume event streams programmatically. Missing for 10: independent/hands-on corroboration of webhook reliability or payload completeness beyond first-party docs.
- [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
- [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”
- [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”
Notion's docs explicitly document webhook subscriptions for real-time events (page updates, property changes, new comments) sent as secure HTTP POST requests, configurable per connection. missing for 10: no independent/hands-on corroboration of webhook reliability or event coverage beyond first-party docs.
- [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
- [claimed-docs] “Whenever a page or database changes, Notion sends a secure HTTP POST request to your webhook endpoint.”
ai-native userHand off work between tools or agents without losing context or information
weight 1 · round to LinearLinear documents extensive hand-off machinery for agentic work: issues can be delegated (not assigned) to AI agents while humans retain ownership, agents behave like workspace members (mentions, comments, docs) so context stays attached to the issue, and MCP/integration connectors (GitHub, Copilot, Codex, Claude, Cursor, Slack) let work flow between tools while Linear remains the shared context hub. Features like 'Write with Agent' (pulls prior updates plus Slack context), checkpoints/version history, guided reviews with before/after screenshots, and Loops updating linked docs/Slack on changes all reinforce continuity across handoffs. missing for 10: independent/hands-on verification that context genuinely survives cross-tool handoffs (all evidence is first-party docs), and no explicit benchmark/comparison of information loss vs other tools
- [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
- [claimed-docs] “Assigning an issue to your app now sets it as the delegate, not the assignee—so humans maintain ownership while agents act on their behalf.”
- [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
- [claimed-docs] “Once connected to Linear, teammates can delegate issues to your agent or mention it in comments.”
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
- [claimed-docs] “If you need to revert to an earlier version, restore to any previous checkpoint from version history.”
- [claimed-docs] “Linear Agent can now set up, run, and test your code before returning its work.”
- [claimed-docs] “The agent opens the app, navigates through a flow, and verifies its implementation. It also captures before-and-after screenshots”
- [claimed-docs] “Linear Agent can now write code using Claude Code and Codex.”
- [claimed-docs] “Connect Cursor to the Linear MCP server”
- [claimed-docs] “Connect Claude to the Linear MCP server”
- [claimed-docs] “Connect GitHub to automate PR workflows, review code in Linear, sync issues and understand your codebase with Linear Agent”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
Notion supports handoff via REST API, webhooks, MCP server/client interoperability (Claude Code, Cursor, Codex), and Agent APIs with session/event history that preserve context across tool boundaries. However, there's no dedicated evidence of cross-agent context preservation guarantees, no independent/hands-on validation of lossless handoff, and community feedback focuses on unrelated pain points rather than confirming this specific capability. missing for 10: independent verification of lossless context transfer between agents/tools, explicit handling of long-running multi-agent handoff scenarios, and hands-on user reports confirming this workflow in practice.
- [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
- [claimed-docs] “Find the Custom Agents your token can access, track their usage, and manage their status and credit limits.”
- [claimed-docs] “Notion MCP lets an MCP client, such as Claude Code, Cursor, or Codex, connect to your Notion workspace through the Model Context Protocol (M…”
- [claimed-docs] “Search content in Notion and connected sources. * Read, create, and update Notion content. * Create pages and databases.”
- [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
- [claimed-docs] “Whenever a page or database changes, Notion sends a secure HTTP POST request to your webhook endpoint.”
- [probe] “official MCP server documented at https://developers.notion.com/docs/mcp”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round drawnLinear ships AI-agent features (Write with Agent for project updates, Loops for automated doc/plan updates, auto-triage/routing of feedback into issues, Linear Agent investigating issues) that surface generated content and suggestions inside the product, per linear-docs-19, linear-docs-38, linear-docs-45, linear-docs-62, linear-docs-95-97. However, these are framed as agentic task-execution/automation rather than analytic 'insights' (e.g., trend analysis, prioritization recommendations, summarization dashboards), and there's no independent/hands-on evidence validating quality of these AI outputs. missing for 10: dedicated insight/analytics generation (e.g., pattern detection across issues, predictive suggestions, summarized health reports) and third-party corroboration of suggestion quality.
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
- [claimed-docs] “When a new issue is reported, Linear Agent can investigate and attempt a fix before it reaches an engineer, reducing the load on your team.”
- [claimed-docs] “Automatically turn conversations and customer feedback into actionable issues that are instantly routed, labeled, and prioritized for the ri…”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
Notion documents AI-native capabilities like Q&A with citations ('Get answers, instantly—with citations'), always-on agents ('Keep work moving 24/7 with agents'), and Notion Agent APIs/MCP that can search, read, and act on workspace content, implying AI-generated insight generation from user data. However, evidence is largely first-party marketing/docs with no independent hands-on account of the quality or depth of these AI-generated insights/suggestions, and no detail on proactive suggestion generation beyond Q&A/agents. Missing for 10: independent corroboration of insight quality, concrete examples of AI-generated suggestions (not just answers/actions), and detail on proactive analytics/insight surfacing.
- [claimed-docs] “Get answers, instantly—with citations.”
- [claimed-docs] “Keep work moving 24/7 with agents.”
- [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
- [claimed-docs] “Find the Custom Agents your token can access, track their usage, and manage their status and credit limits.”
- [claimed-docs] “Search content in Notion and connected sources. * Read, create, and update Notion content. * Create pages and databases.”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to LinearLinear's "Loops" feature explicitly lets users describe a job in plain language and set it to run on a schedule or in response to events, enabling autonomous background automations (e.g., updating docs, posting Slack updates, monitoring initiatives) without manual triggering. This is well documented across multiple changelog entries describing scheduling, event triggers, and recurring workflows. Missing for 10: independent/hands-on verification of reliability at scale and no third-party community confirmation of autonomous background execution in practice.
- [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
- [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
- [claimed-docs] “You can now add a loop to Favorites”
Notion's docs claim agent capabilities ('Keep work moving 24/7 with agents') plus a dedicated Agent API with sessions, event history, and Custom Agents that can be tracked/managed via token — suggesting agents that operate somewhat autonomously in the background. Webhooks and internal-connection API tokens also support event-driven automations that fire without user intervention. However, the MCP security guidance recommends requiring human confirmation before content-changing actions, which cuts against true unattended autonomy, and there's no detail on native scheduled/triggered workflow automations or independent verification of 24/7 unattended operation. Missing for 10: documentation of native scheduled/cron-style automations, evidence agents can act without confirmation gates, and independent/hands-on corroboration of reliable background execution.
- [claimed-docs] “Keep work moving 24/7 with agents.”
- [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
- [claimed-docs] “Find the Custom Agents your token can access, track their usage, and manage their status and credit limits.”
- [claimed-docs] “The connection can access only Custom Agents that are explicitly shared with it.”
- [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
- [claimed-docs] “Whenever a page or database changes, Notion sends a secure HTTP POST request to your webhook endpoint.”
- [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
- [claimed-docs] “Enable confirmation before actions that change content. This lets you review an action before the MCP client runs it.”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to LinearLinear ships a built-in 'Linear Agent' that users can delegate issues to directly (assign/mention), which writes code via Claude Code/Codex, edits text, runs Loops for recurring work, drafts project updates, and shows delegated work status in My Issues, all documented extensively in first-party changelog docs. missing for 10: independent/hands-on verification beyond vendor changelog, and clearer detail on reliability/limits of the built-in assistant in real-world use.
- [claimed-docs] “Linear Agent can now write code using Claude Code and Codex.”
- [claimed-docs] “Linear Agent can now set up, run, and test your code before returning its work.”
- [claimed-docs] “We’ve also added section under My Issues → Assigned for your delegated issues. It shows the status of each coding session, and gives you a q…”
- [claimed-docs] “Once connected to Linear, teammates can delegate issues to your agent or mention it in comments.”
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
- [claimed-docs] “You can now edit text with Linear Agent, and use Loops to keep docs and project descriptions up-to-date.”
- [claimed-docs] “When a new issue is reported, Linear Agent can investigate and attempt a fix before it reaches an engineer, reducing the load on your team.”
- [claimed-docs] “@Linear can you take a stab at this?”
Notion markets and documents a built-in AI assistant/agent layer ('Get answers, instantly—with citations', 'Keep work moving 24/7 with agents') plus first-party Agent APIs for sessions, chat, streaming replies, and Custom Agents management, showing the assistant is a native, delegable feature rather than a third-party bolt-on. Missing for 10: independent/hands-on user reports validating real-world task delegation quality and reliability, and more detail on in-app assistant UX beyond marketing copy and API docs.
- [claimed-docs] “Get answers, instantly—with citations.”
- [claimed-docs] “Keep work moving 24/7 with agents.”
- [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
- [claimed-docs] “Find the Custom Agents your token can access, track their usage, and manage their status and credit limits.”
- [claimed-docs] “The connection can access only Custom Agents that are explicitly shared with it.”
ai-native userOperate the product with natural-language commands
weight 2 · round to LinearLinear supports natural-language interaction extensively: users can @mention Linear Agent, describe jobs in plain language for Loops, use 'Write with Agent' to draft updates, and delegate issues via comments in natural language (linear-docs-11, -19, -36, -41, -68). This is well documented across multiple first-party changelog entries and the agents.md docs, but missing for 10: independent/hands-on evidence of natural-language command accuracy or limitations, and no dedicated NL command palette/chat interface separate from agent-delegation workflows.
- [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
- [claimed-docs] “Once connected to Linear, teammates can delegate issues to your agent or mention it in comments.”
- [claimed-docs] “@Linear can you take a stab at this?”
- [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
- [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
Notion supports natural-language operation via its AI agents, MCP integration (usable by Claude Code, Cursor, Codex), and Notion Agent APIs that let clients read/create/update content and start chat sessions with streamed replies — a strong agentic surface. However, this is mostly mediated through third-party MCP clients or the Notion AI assistant rather than a built-in native NL command interface across the whole product, and there's no independent/hands-on evidence confirming reliability of these NL-driven actions. missing for 10: independent verification of natural-language command accuracy/reliability, evidence of NL commands operating directly within Notion's own UI (not just via external MCP clients or agent APIs).
- [claimed-docs] “Get answers, instantly—with citations.”
- [claimed-docs] “Keep work moving 24/7 with agents.”
- [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
- [claimed-docs] “Notion MCP lets an MCP client, such as Claude Code, Cursor, or Codex, connect to your Notion workspace through the Model Context Protocol (M…”
- [claimed-docs] “Search content in Notion and connected sources. * Read, create, and update Notion content. * Create pages and databases.”
- [claimed-docs] “A Notion Skill is a page you own with instructions for a repeatable workflow. You can maintain it yourself or ask an assistant to do it for …”
- [probe] “official MCP server documented at https://developers.notion.com/docs/mcp”
ai-native userBuild and configure my own custom AI agent within the product
weight 2 · round to NotionLinear offers in-product mechanisms for creating custom agent-like automation: Loops let users 'describe the job in plain language' and set it to run on a schedule or event (linear-docs-36/95-100), and Skills let teams codify and share recurring agent workflows (linear-docs-23/46). Linear also documents a developer-facing Agents API for building agents that behave like workspace members (assignable, mentionable, can comment) (linear-docs-16, linear-docs-54/64/75/90/94). This is meaningful but falls short of a full custom-agent builder with model/tool selection or a dedicated no-code agent studio. Missing for 10: no evidence of choosing/configuring underlying models or custom toolsets, no dedicated 'agent builder' UI beyond Loops/Skills, and no independent hands-on confirmation of ease-of-use.
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
- [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
- [claimed-docs] “Sharing a skill helps your team standardize recurring workflows like writing specs, running weekly planning, or drafting updates.”
- [claimed-docs] “We now support sharing skills with your team so great personal workflows can become shared team process.”
- [claimed-docs] “Build agents that can investigate incidents, monitor SLAs, or analyze customer feedback.”
- [claimed-docs] “How to best integrate an AI agent into Linear”
- [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
- [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
- [claimed-docs] “app:assignable | Allow the app to be assigned as a delegate on issues and made a member of projects app:mentionable | Allow the app to be me…”
Notion's developer docs describe a distinct 'Custom Agents' capability with session-based chat, streaming replies, action confirmation, and access/usage management (notion-docs-21, notion-docs-22, notion-docs-29), plus marketing language about 'agents' keeping work moving 24/7 (notion-docs-8), indicating users/developers can build and manage their own AI agents in the product. However, the evidence pack lacks detail on how deeply an end user can configure agent persona, tool access, or instructions beyond access-sharing and credit limits. missing for 10: detailed documentation of persona/instruction configuration, tool-selection UI, and independent hands-on confirmation of building a custom agent end-to-end.
- [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
- [claimed-docs] “Find the Custom Agents your token can access, track their usage, and manage their status and credit limits.”
- [claimed-docs] “The connection can access only Custom Agents that are explicitly shared with it.”
- [claimed-docs] “Keep work moving 24/7 with agents.”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnLinear's GraphQL API supports introspection and is explorable/queryable via Apollo Studio Explorer with no login required, effectively an interactive reference with runnable queries, plus published docs with sample queries/mutations and an SDK. However, this is a third-party hosted explorer rather than a first-party embedded interactive API reference, and there's no evidence of runnable examples directly within Linear's own developer docs site. missing for 10: first-party embedded interactive API console with runnable examples on developers.linear.app itself, independent/hands-on confirmation of the Apollo Explorer experience, broader runnable example coverage beyond basic query/mutation snippets.
- [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
- [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
- [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”
- [claimed-docs] “query Issue { issue(id: "BLA-123") { id title description } }”
- [claimed-docs] “const myIssues = await me.assignedIssues();”
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “Learn how to use the GraphQL API to query and mutate your data”
Notion publishes a full OpenAPI spec and a quickstart guide that walks through making a live API request in minutes, indicating a structured, testable API reference exists, but there is no explicit evidence of an in-browser 'try it now' runnable console or interactive playground beyond the openapi.json and quickstart docs. missing for 10: explicit interactive try-it-in-browser console, independent confirmation of runnable examples working out-of-box.
- [probe] “PROBE openapi: HTTP 200 at https://developers.notion.com/openapi.json — contains "openapi" key”
- [claimed-docs] “create a personal access token, make your first API request, and see a new page appear in your workspace in under two minutes”
- [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to NotionLinear's API is GraphQL, not OpenAPI/REST, but it explicitly supports schema introspection and publishes a full schema SDL file in the linear/linear GitHub repo, plus an explorable schema via Apollo Studio — giving AI-native users machine-readable access to the API's shape without needing a human-written spec. This satisfies the intent of a downloadable machine-readable spec via GraphQL introspection/SDL rather than OpenAPI itself. missing for 10: no explicit OpenAPI/Swagger document, no single-click 'download spec' artifact, and no independent/community confirmation of using the introspection or SDL file in practice.
- [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
- [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “Linear's public API is built using GraphQL.”
Notion hosts a downloadable OpenAPI spec at developers.notion.com/openapi.json (confirmed HTTP 200 with 'openapi' key), alongside an llms.txt machine-readable docs index, giving AI-native users direct access to a standard, machine-readable API spec. missing for 10: no independent third-party confirmation of spec completeness/versioning beyond the probe check.
- [probe] “PROBE openapi: HTTP 200 at https://developers.notion.com/openapi.json — contains "openapi" key”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.notion.com/llms.txt # Notion Docs - [Overview](https://developers.notion.com/guides/get-star…”
- [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round to LinearLinear's own docs explicitly state its GraphQL API 'doesn't have versioning like many REST APIs,' but they do document a deprecation policy: use of the @deprecated schema directive, proactive outreach for breaking changes, and changelog entries tagged [API]. This satisfies the 'documented deprecation policy' half of the story but directly contradicts the 'versioned APIs' half. Missing for 10: an actual versioning scheme (e.g., v1/v2 endpoints or dated API versions), and independent/community corroboration that deprecation notices are reliably honored in practice.
- [claimed-docs] “Docs, "Deprecations": "Linear's GraphQL API doesn't have versioning like many REST APIs... we take breaking changes and deprecations serious…”
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
Notionnone0/10The evidence pack shows Notion's REST API, OAuth, webhooks, and OpenAPI spec exist, but none of the citations mention API versioning conventions (e.g., a Notion-Version header) or any documented deprecation policy for breaking changes. Missing for 10: explicit version header documentation, deprecation timeline commitments, migration guides for version changes.
ai-native userThe documented API rate limits and concurrency caps before building automation at scale
weight 2 · round to LinearLinear's developer docs explicitly publish per-auth-type rate limits (API key, OAuth, unauthenticated), leaky-bucket refill behavior, complexity limits, and rate-limit response headers, giving AI-native builders concrete numbers to design automation around. Missing for 10: explicit documented concurrency caps (max simultaneous requests/connections) beyond hourly request quotas, and no independent/hands-on confirmation that these limits hold in practice at scale.
- [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”
Notionnone0/10The evidence pack covers API capabilities, auth models, webhooks, and MCP integration, but nowhere documents specific rate limits, request-per-second caps, or concurrency limits for the REST API. No source states numeric thresholds or throttling behavior that an automation builder would need to plan at scale.
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round drawnLinear's GraphQL API, SDK, and webhook system (linear-docs-49,53,51) provide the technical means to script bulk changes across issues, and there's a documented bulk import capability (linear-docs-47). However, there is no explicit documentation of a dedicated bulk-edit UI, batch mutation endpoints, or AI-agent-driven bulk operation workflow across many items at once. missing for 10: explicit bulk-edit/multi-select UI docs, batch/bulk GraphQL mutations, and any agent or automation example operating on multiple items simultaneously.
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
- [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
- [claimed-docs] “Import data from other services into Linear”
- [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”
Notion's REST API and MCP integration let scripts/agents read, create, and update pages and databases programmatically (notion-docs-1, notion-docs-13, notion-docs-26), which enables looping over many items via custom code, but there is no documented native batch/bulk endpoint or bulk-update mechanism in the evidence pack. Missing for 10: explicit bulk/batch API endpoints, rate-limit guidance for large-scale operations, and independent confirmation that bulk automation works reliably at scale.
- [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
- [claimed-docs] “you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more”
- [claimed-docs] “Search content in Notion and connected sources. * Read, create, and update Notion content. * Create pages and databases.”
- [claimed-docs] “create a personal access token, make your first API request, and see a new page appear in your workspace in under two minutes”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to LinearLinear's 'Loops' feature explicitly lets users describe a job in plain language and choose to run it on a schedule or in response to an event (e.g., initiative/project/cycle changes), with concrete examples like auto-updating docs or posting Slack messages when a target date changes. This is reinforced by webhook support for event-driven automation via the API. Missing for 10: independent/hands-on corroboration beyond vendor docs, and detail on the breadth of definable trigger conditions/rules.
- [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
- [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
- [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
- [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”
Notion's platform supports event-driven automation via webhooks (subscribing to page/property/comment changes and POSTing to an endpoint) plus a REST API and agent APIs to act on those events, which lets an AI-native user build 'when X happens, do Y' pipelines. However, this requires external code/infra to interpret webhook payloads and execute actions — there's no documented native no-code 'if this then that' rule builder in the evidence, only developer-facing webhook + API primitives. Missing for 10: evidence of a built-in visual automation/rules engine, filtering conditions on triggers, and independent confirmation that webhook-driven automations work reliably in practice.
- [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
- [claimed-docs] “Whenever a page or database changes, Notion sends a secure HTTP POST request to your webhook endpoint.”
- [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
- [claimed-docs] “Find the Custom Agents your token can access, track their usage, and manage their status and credit limits.”
- [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to LinearLinear's 'Loops' feature is explicitly designed for recurring agent workflows: users describe a job and choose to run it 'on a schedule or in response to an event,' with examples like auto-updating launch plans and posting Slack updates when project dates change. Docs also show loops can be shared as team-wide skills and pinned/favorited for ongoing use, covering both scheduling and workflow automation depth. Missing for 10: independent/hands-on confirmation that scheduled loops reliably trigger as configured, and technical detail on scheduling granularity or failure handling.
- [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
- [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
- [claimed-docs] “Sharing a skill helps your team standardize recurring workflows like writing specs, running weekly planning, or drafting updates.”
- [claimed-docs] “We now support sharing skills with your team so great personal workflows can become shared team process.”
- [claimed-docs] “You can now add a loop to Favorites”
Notionnone0/10Evidence shows Notion's API/webhooks support event-driven automation (page changes, comments) and scripted API access via PATs, but there is no documented native mechanism for scheduling recurring/time-based jobs or workflows within Notion itself — webhooks fire on data changes, not on a schedule. Missing for 10: any documented cron-like scheduler, recurring automation trigger, or timed job feature.
- [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
- [claimed-docs] “Whenever a page or database changes, Notion sends a secure HTTP POST request to your webhook endpoint.”
- [claimed-docs] “Personal access tokens (PATs) are user-scoped tokens for scripts, CLI workflows, Workers, and tools that should act as one Notion user.”
- [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
ai-native userVersion, review, and roll back my automations
weight 1 · round to LinearLinear offers general version history/checkpoint restore for work (linear-docs-35) and rich review tooling for agent-produced code changes (guided reviews, diff rendering — linear-docs-7, linear-docs-72), which partially satisfies the 'version, review, rollback' need for AI-generated work. However there is no evidence of version control, review, or rollback specifically for the automations/Loops themselves (the scheduled/event-driven workflows) — only their outputs (documents, code) get versioned. Missing for 10: explicit versioning of Loop/automation definitions, audit trail of automation changes, and a dedicated rollback mechanism for the automation logic itself rather than just its output artifacts.
- [claimed-docs] “If you need to revert to an earlier version, restore to any previous checkpoint from version history.”
- [claimed-docs] “Guided Reviews break diffs into focused sections with explainers on what changed and why.”
- [claimed-docs] “Images, fonts, Markdown, and PDFs now render directly inside Linear diffs.”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
Notionnone0/10Evidence shows Notion has automation-adjacent features (API-driven agents, MCP action confirmation) but nothing about versioning automation definitions, reviewing change history, or rolling back automations to a prior state. The closest item (notion-docs-28) only covers per-action confirmation, not version control or rollback of the automation itself.
- [claimed-docs] “Enable confirmation before actions that change content. This lets you review an action before the MCP client runs it.”
- [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
- [claimed-docs] “Find the Custom Agents your token can access, track their usage, and manage their status and credit limits.”
Automation workflows — building automations — triggers, actions, branching, schedulingAutomation workflows
Building automations — triggers, actions, branching, scheduling
Ai task automation
ai-native userHave AI automatically triage and prioritize incoming bugs and tasks
weight 2 · round to LinearLinear docs explicitly describe AI-driven triage: incoming feedback/issues are 'instantly routed, labeled, and prioritized for the right team,' and Linear Agent can 'investigate and attempt a fix before it reaches an engineer,' plus a Priority tab surfaces what needs attention. These directly match the automatic triage/prioritization story. Missing for 10: independent/hands-on evidence validating triage accuracy or reliability beyond vendor changelog claims.
- [claimed-docs] “Automatically turn conversations and customer feedback into actionable issues that are instantly routed, labeled, and prioritized for the ri…”
- [claimed-docs] “When a new issue is reported, Linear Agent can investigate and attempt a fix before it reaches an engineer, reducing the load on your team.”
- [claimed-docs] “The new Priority tab separates what needs your attention from what can wait, so something like a review blocking a release never gets buried…”
Notion documents AI agents ('Keep work moving 24/7 with agents') and a REST API with webhooks that could be wired to auto-triage or prioritize tasks/bugs in a database, but there is no evidence of an out-of-the-box bug/task triage or prioritization feature — this would require custom building. Missing for 10: dedicated bug/task triage feature, evidence of automatic prioritization logic, and any hands-on confirmation this works as described.
- [claimed-docs] “Keep work moving 24/7 with agents.”
- [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
- [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
- [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
ai-native userHave my in-app AI assistant learn my tone, shorthand, and preferences to tailor its output
weight 1 · round drawnLinearnone0/10Evidence shows Linear Agent can draft updates, edit text, and run automated 'Loops', but nothing describes it learning an individual user's tone, shorthand, or personal preferences to tailor future outputs — personalization/memory of style is never mentioned.
Notionnone0/10Evidence covers Notion's AI agent APIs, MCP integration, and general search/citations features, but nothing describes the AI assistant learning a user's personal tone, shorthand, or writing preferences to tailor output. Notion Skills (notion-docs-27) let users author explicit workflow instructions, but that's manual configuration, not adaptive learning of personal style/preferences.
Workflow automation
engineerAuto-generate a changelog for each release so shipping progress is easy to review
weight 1 · round to LinearLinear explicitly documents an auto-generate release notes option in pipeline settings, directly matching the story of auto-generating a changelog per release. missing for 10: no detail on customization/format of generated changelogs, no independent/hands-on corroboration beyond the single changelog entry.
- [claimed-docs] “Choose to auto-generate release notes in pipeline settings so your changelog is always up to date.”
product managerBuild multi-step automations without writing code
weight 2 · round to LinearLinear's 'Loops' feature lets users describe a recurring job in plain language and choose a schedule or event trigger, with multi-step behavior like updating documents and posting Slack messages when conditions change—exactly a no-code automation builder usable by a PM. Additional context (skills, agent-based investigation/monitoring) reinforces no-code configurability. missing for 10: independent/hands-on evidence of a PM successfully building complex branching automations, and detail on conditional/branching logic depth
- [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
- [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
- [claimed-docs] “Build agents that can investigate incidents, monitor SLAs, or analyze customer feedback.”
- [claimed-docs] “We now support sharing skills with your team so great personal workflows can become shared team process.”
- [claimed-docs] “Sharing a skill helps your team standardize recurring workflows like writing specs, running weekly planning, or drafting updates.”
Notion advertises 'agents' that 'keep work moving 24/7' and 'Notion Skills' as reusable, no-code workflow instructions, plus Custom Agents accessible via API, hinting at some no-code automation capability for non-developers. However, most of the automation-related evidence (REST API, webhooks, MCP servers, PATs) is explicitly developer/code-oriented, and there is no documentation of a native drag-and-drop or point-and-click multi-step automation builder for PMs. Missing for 10: a dedicated no-code automation builder UI, concrete PM-facing multi-step workflow examples, and independent corroboration that non-technical users can chain multiple actions without scripting.
- [claimed-docs] “Keep work moving 24/7 with agents.”
- [claimed-docs] “A Notion Skill is a page you own with instructions for a repeatable workflow. You can maintain it yourself or ask an assistant to do it for …”
- [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
- [claimed-docs] “Find the Custom Agents your token can access, track their usage, and manage their status and credit limits.”
engineerBuild trigger-and-action automation rules to eliminate repetitive manual steps
weight 3 · round to LinearLinear's 'Loops' feature explicitly lets users describe a job in plain language and choose to run it on a schedule or in response to an event, automating recurring work like updating docs, posting Slack messages, or monitoring initiatives — a direct trigger-and-action automation capability, further extensible via webhooks and the GraphQL API for custom automations. missing for 10: independent/hands-on verification of Loops reliability at scale, and more detail on the breadth of available trigger/action types beyond the examples shown.
- [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
- [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
- [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
- [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”
Notion's REST API, webhooks, and internal/public connections let engineers build custom trigger-and-action automations (subscribe to page/property changes, then read/create/update content programmatically), and third-party integrations (GitHub, Loom, Tableau) extend this further. However, this is a DIY/code-first approach via API+webhooks rather than a native no-code trigger-action rules builder inside Notion itself. Missing for 10: evidence of a built-in visual automation/rules engine (if-this-then-that) inside the product, and independent verification that engineers successfully use these APIs for production automation.
- [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
- [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
- [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
- [claimed-docs] “Whenever a page or database changes, Notion sends a secure HTTP POST request to your webhook endpoint.”
- [claimed-docs] “Keep your GitHub and Notion workflows in sync”
engineerCreate a workflow that runs on a schedule or recurring event to handle routine team work
weight 2 · round to LinearLinear's 'Loops' feature explicitly lets users describe a job in plain language and choose to run it on a schedule or in response to an event, targeting recurring team work like weekly planning, doc updates, or launch plan syncing (linear-docs-11, linear-docs-36, linear-docs-23, linear-docs-95, linear-docs-96, linear-docs-100). This directly matches the story of scheduled/recurring workflow automation for routine team tasks. missing for 10: independent/hands-on verification of Loops reliability and no detail on error handling or monitoring of scheduled runs.
- [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
- [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
- [claimed-docs] “Sharing a skill helps your team standardize recurring workflows like writing specs, running weekly planning, or drafting updates.”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
- [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
Notion exposes a REST API, personal access tokens, and webhooks for event-driven automation (e.g., page/database changes), which engineers could wire into external cron jobs or agent workflows for routine team tasks, but there is no documented native scheduling/cron trigger inside Notion itself — webhooks are event-triggered, not time-based. missing for 10: native schedule/cron trigger, built-in recurring-job runner, first-party example of a scheduled automation using the API.
- [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
- [claimed-docs] “Personal access tokens (PATs) are user-scoped tokens for scripts, CLI workflows, Workers, and tools that should act as one Notion user.”
- [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
- [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
- [claimed-docs] “Whenever a page or database changes, Notion sends a secure HTTP POST request to your webhook endpoint.”
- [probe] “PROBE openapi: HTTP 200 at https://developers.notion.com/openapi.json — contains "openapi" key”
ai-native userWhat happens—extra charges, throttling, or a hard stop—when I exceed my plan's automation or API call limits
weight 3 · round to LinearLinear's docs publish exact per-auth-type API rate limits, response headers (e.g. X-RateLimit-Requests-Limit) and a leaky-bucket refill model, and separately allow admins to set spend limits for AI agent/automation usage that reset periodically — together these give a user real visibility into automation/API limits. However, the pack doesn't explicitly spell out the concrete consequence of exceeding a limit (e.g. exact 429 throttling behavior, whether overages incur extra charges, or a hard stop for automation/Loops usage), so the full 'what happens when I exceed' picture is only partially documented. Missing for 10: explicit statement of throttling/error response code, confirmation of no/optional overage billing, and documented consequence for exceeding automation (Loops/agent) usage specifically rather than just spend caps.
- [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
- [claimed-docs] “Admins can also set workspace-wide and per-user spend limits that reset daily, weekly, or monthly.”
Notionnone0/10No evidence pack item discusses rate limits, throttling, overage charges, or hard stops for API/automation usage—only general API capabilities, agent 'credit limits' mention without specifics, and integration lists are present. This is an applicable axis for an API-driven product, but no documentation of what happens when limits are exceeded is provided.
Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaboration
Working as a team — sharing, comments, roles, simultaneous editing
Cross tool sync
designerKeep project status updated from my design tool without switching apps
weight 2 · round to NotionLinearnone0/10The evidence pack shows Linear's API, webhooks, GraphQL SDK, and general integrations (GitHub, Slack, Okta) but contains no mention of a Figma or other design-tool plugin/integration that lets designers update project status without leaving their design tool. Missing for 10: any Figma/design-tool plugin, any documented design-tool-to-Linear status sync, or third-party evidence of such a workflow.
Notion offers a generic REST API, webhooks, and integrations (e.g. Canva, Sketch) that let designers view/share design assets in Notion and could theoretically be used to sync status via custom automation, but there is no evidence of a built-in, native workflow where a design tool directly updates a Notion project status field without switching apps. Missing for 10: a documented direct integration (e.g. Figma/Canva plugin) that writes status/property updates back to Notion, and any hands-on confirmation that such a workflow works in practice.
- [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
- [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
- [claimed-docs] “View and share Canva designs in Notion”
- [claimed-docs] “View and share Sketch designs in Notion”
- [claimed-docs] “Whenever a page or database changes, Notion sends a secure HTTP POST request to your webhook endpoint.”
Docs knowledge
product managerCreate and organize shared docs and notes alongside my project work
weight 3 · round to NotionLinear supports document creation and organization tied to projects/issues (teams can create documents from home page, add existing documents to projects/issues, group into sections, comment on docs, mobile doc editing) which covers shared docs alongside project work. However, evidence for cross-team/workspace-wide doc organization, folder hierarchies, or dedicated doc search/collaboration features (e.g. co-editing, version history for docs specifically) is thin. missing for 10: evidence of broader doc organization features (folders/wikis beyond project linkage), real-time co-editing, and independent user feedback confirming docs experience.
- [claimed-docs] “Teams can create documents directly from their home page, add existing documents from projects and issues, and group resources into sections…”
- [claimed-docs] “Document creation and editing are now available in Linear's iOS and Android apps.”
- [claimed-docs] “You can now comment directly on text or images in issue descriptions.”
- [claimed-docs] “Use callout components to draw attention to important information in issue and project descriptions, as well as documents.”
Notion's core product is exactly this: shared docs/notes organized alongside databases and project tracking in 'one system of record,' and community evidence confirms real-world use as wiki, project tracker, and issue tracker alongside notes. Minor caveats exist (comm-6 notes friction at scale, comm-8 a legacy block-limit complaint) but the core capability is well established. Missing for 10: independent benchmarking of doc/project integration depth and resolution of the 'jack of all trades' scaling complaints.
- [claimed-docs] “Bring everything into one system of record.”
- [community] “Notion feels like it's got this serious range from individuals up to teams at large enterprises. It's incredibly flexible and configurable..…”
- [community] “Notion is currently a jack of all trades and master of none. We have tried to use it as a wiki, project tracker, issue tracker, CRM & spread…”
- [community] “We use it to keep track of all of our tasks and projects... notifications are still hit or miss... Search still needs some love... I'd love …”
- [community] “Glad to see this here, it's a very well-built product that finds the perfect balance between strict JIRA/PM tools and completely unstructure…”
In context discussion
engineerComment directly on specific text or images within an item's description
weight 2 · round to LinearLinear's own changelog explicitly states the exact capability: 'You can now comment directly on text or images in issue descriptions,' directly matching the story. missing for 10: no independent/hands-on corroboration beyond the vendor changelog entry.
- [claimed-docs] “You can now comment directly on text or images in issue descriptions.”
The evidence only shows that Notion's API can read/create/update generic 'comments' as one of the object types alongside pages and databases (notion-docs-1, notion-docs-13), but there is no documentation or community evidence confirming the specific capability of inline commenting on selected text or images within a page description. Missing for 10: explicit documentation of block/inline text commenting, image-specific comment anchoring, and any hands-on confirmation that comments attach to specific text/image selections rather than whole pages/blocks generically.
- [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
- [claimed-docs] “you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more”
Real time sync
engineerSee teammates' changes reflected instantly across open sessions without refreshing
weight 3 · round to NotionLinearnone0/10The evidence pack contains no documentation or community reports describing real-time, no-refresh syncing of teammates' changes across open sessions (e.g., live cursors, instant issue updates, presence). References to webhooks (linear-docs-51/52) describe external HTTP push notifications for integrations, not in-app live UI updates, and speed-related comments (linear-comm-6) address load times, not multi-session sync.
Community feedback confirms Notion's real-time collaborative editing is a strong point ('really good real-time collaboration', 'collaborative components feel really powerful'), but other reports describe lag and even a page refresh wiping unsaved work, suggesting real-time sync isn't always seamless. No first-party documentation explicitly describes the live-sync/websocket mechanism for instant cross-session updates. missing for 10: official docs on real-time sync architecture, hands-on verification of instant updates without refresh, resolution of documented lag/data-loss complaints.
- [community] “For now I use Notion with the hopes they implement it eventually [offline read-only mode]. I can't consider switching to a self hosted alter…”
- [community] “Glad to see this here, it's a very well-built product that finds the perfect balance between strict JIRA/PM tools and completely unstructure…”
- [community] “I love Notion but the speed, or rather lack of, is killing me daily. Last Friday I was taking some notes, and suddenly the page refreshed an…”
Team chat
engineerChat with my team directly inside the same tool I plan work in
weight 2 · round to LinearLinear supports asynchronous team collaboration via comments on issues, documents, and images (linear-docs-24, linear-docs-22) and @mentions (linear-docs-54), plus Slack integration for notifications (linear-docs-61, linear-docs-81), but there is no evidence of a native real-time chat/messaging feature inside Linear itself — collaboration is comment-based, not conversational chat. missing for 10: a dedicated in-app chat/messaging surface, evidence of synchronous team chat, and any first-party claim positioning Linear as a chat tool rather than relying on comments/Slack.
- [claimed-docs] “You can now comment directly on text or images in issue descriptions.”
- [claimed-docs] “Teams can create documents directly from their home page, add existing documents from projects and issues, and group resources into sections…”
- [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
- [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”
- [claimed-docs] “Create issues from Slack messages and sync threads”
Integrations — connecting to other tools — breadth and depth of built-in integrationsIntegrations
Connecting to other tools — breadth and depth of built-in integrations
App ecosystem
engineerKeep tasks bi-directionally synced with my code repository's issue tracker instead of duplicating data
weight 2 · round drawnLinear's changelog references GitHub-synced issues (opening them in GitHub) and syncing review requests/teams with GitHub, plus a public GraphQL API and webhooks that could be used to build two-way sync with an external tracker, but there is no explicit documentation describing full bi-directional field sync (status, description, comments) that eliminates duplicate data entry with a repo issue tracker. Missing for 10: explicit doc/feature description of two-way sync with GitHub Issues (not just PR/review linking), independent/hands-on confirmation that sync avoids duplication, and coverage beyond GitHub (e.g., GitLab).
- [claimed-docs] “Open a GitHub-synced issue in GitHub with OG”
- [claimed-docs] “You can now assign reviews to GitHub teams.”
- [claimed-docs] “You can now assign reviews to GitHub teams. Review requests assigned to your GitHub teams appear in a dedicated section of the Reviews inbox…”
- [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
- [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
Notion lists a GitHub integration ('Keep your GitHub and Notion workflows in sync') and offers a general REST API plus webhooks that could be used to build custom bi-directional sync between Notion databases and an issue tracker, but there is no documented native two-way sync of task/issue state (e.g., status changes propagating both directions) — the GitHub integration description is thin and unverified beyond a marketing tagline, and an older community comment even complains Notion 'does not have a GitHub integration.' missing for 10: concrete documentation of bi-directional field/status sync with GitHub Issues (or Jira/Linear), and independent confirmation the integration goes beyond simple embeds/linking.
- [claimed-docs] “Keep your GitHub and Notion workflows in sync”
- [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
- [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
- [claimed-docs] “Whenever a page or database changes, Notion sends a secure HTTP POST request to your webhook endpoint.”
- [community] “Why does Notion not have a GitHub integration? Kind of a dealbreaker for using it on any tech team unless you just want a wiki.”
engineerSee my assigned tasks from multiple project management tools in one unified view
weight 2 · round drawnLinearnone0/10Evidence shows Linear integrates with GitHub, Slack, Okta, and supports one-time data import from other services (linear-docs-47), but there is no evidence of a unified cross-tool task view aggregating assignments from multiple external project management tools (e.g., Jira, Asana) into one dashboard. Linear positions itself as a replacement for such tools rather than an aggregator.
- [claimed-docs] “Import data from other services into Linear”
Notionnone0/10Evidence shows Notion's API and integrations directory (GitHub, Loom, Tableau, Mixpanel, Canva, etc.) but none of these are project-management tools like Jira, Asana, or Trello, and there is no documented feature for pulling assigned tasks from multiple external PM tools into a single unified view. Community comments even note the historical lack of GitHub/PM integrations as a dealbreaker, with no counter-evidence of a task-aggregation feature being added.
- [claimed-docs] “Keep your GitHub and Notion workflows in sync”
- [claimed-docs] “Extend Notion with connections that sync your data, automate workflows, and connect your favorite tools.”
- [claimed-docs] “View Mixpanel boards, reports and charts inside Notion”
- [community] “Why does Notion not have a GitHub integration? Kind of a dealbreaker for using it on any tech team unless you just want a wiki.”
- [community] “Notion could as well [integrate with Mattermost/discord] but they are a slow moving beast with different priorities.”
engineerConnect common tools like Slack, GitHub, and Google Drive natively
weight 2 · round to LinearLinear's integrations directory explicitly documents native Slack (create issues from Slack messages, sync threads, Slack notifications), GitHub (automate PR workflows, review code, sync issues, assign reviews to GitHub teams), and Google Drive-adjacent file referencing plus a broad app ecosystem (Figma, GitLab, Sentry, Datadog, Notion, etc.), backed by OAuth/API infrastructure for deeper connections. Missing for 10: explicit first-party documentation of a native Google Drive integration specifically (only general file/import references appear) and independent hands-on confirmation of these integrations' reliability.
- [claimed-docs] “Connect GitHub to automate PR workflows, review code in Linear, sync issues and understand your codebase with Linear Agent”
- [claimed-docs] “Create issues from Slack messages and sync threads”
- [claimed-docs] “You can now assign reviews to GitHub teams.”
- [claimed-docs] “You can now assign reviews to GitHub teams. Review requests assigned to your GitHub teams appear in a dedicated section of the Reviews inbox…”
- [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”
- [claimed-docs] “Third-party app approvals are now available on paid Linear plans, allowing admins to review and approve apps before they're installed.”
- [claimed-docs] “Learn how to reference a file in markdown content, or upload with the API”
- [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
Notiondisputedcontradicted3/10Notion's dev docs describe a general integrations framework (public/internal connections, OAuth, webhooks, marketplace) that could support connectors to tools like Slack, GitHub, or Google Drive, but no evidence names these specific integrations as built-in. A direct community report explicitly states Notion lacks a native GitHub integration, calling it a dealbreaker for tech teams, which concretely contradicts any claim of native connectivity to common engineering tools. Missing for 10: explicit documentation or first-party listing of Slack, GitHub, and Google Drive integrations, and independent confirmation they work natively without third-party glue.
- [claimed-docs] “Public connections use OAuth 2.0 for authentication... Public connections must undergo a Notion security review before being listed on the M…”
- [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
- [claimed-docs] “Public connections use OAuth 2.0 for authentication. At creation time, you choose their installation scope”
- [community] “Why does Notion not have a GitHub integration? Kind of a dealbreaker for using it on any tech team unless you just want a wiki.”
product managerConnect my workspace to thousands of third-party tools via an app marketplace
weight 2 · round drawnLinear ships a documented integrations/app directory (GitHub, Slack, Figma, Salesforce, Sentry, Datadog, Notion, Airbyte, Fivetran, Cursor, ChatGPT, Claude, Jira migration, etc.), an OAuth app creation flow, and admin-level third-party app approval controls, which together function like a marketplace for connecting external tools. However, the evidence shows a curated directory of a few dozen named integrations plus a general public GraphQL/OAuth API for building custom ones, not literally 'thousands' of pre-built marketplace apps as the story implies. Missing for 10: evidence of marketplace scale (thousands of listed apps), a searchable public app store UI, and independent confirmation of ecosystem breadth beyond Linear's own docs.
- [claimed-docs] “Connect GitHub to automate PR workflows, review code in Linear, sync issues and understand your codebase with Linear Agent”
- [claimed-docs] “Create issues from Slack messages and sync threads”
- [claimed-docs] “Create and link issues directly from Figma”
- [claimed-docs] “Automate your Merge Request workflow”
- [claimed-docs] “Build custom dashboards and analytics from issue and project data”
- [claimed-docs] “Delegate issues to Codex directly from Linear”
- [claimed-docs] “Turn issues into pull requests with Cursor cloud agents”
- [claimed-docs] “Automate work from issue to tested PR with Devin”
- [claimed-docs] “Create Linear issues from Datadog Cases and Monitors”
- [claimed-docs] “Smoothly transition from Jira to Linear”
- [claimed-docs] “Sync your Linear data with the Fivetran connector”
- [claimed-docs] “Create Linear issues from Salesforce cases”
- [claimed-docs] “Connect Linear to Airbyte and consolidate data in data warehouses, lakes, and databases”
- [claimed-docs] “Third-party app approvals are now available on paid Linear plans, allowing admins to review and approve apps before they're installed.”
- [claimed-docs] “Use URL parameters to send users directly to a pre-filled Create OAuth App form in Linear. An equivalent JSON manifest format lets you store…”
Notion's docs confirm a public marketplace model with OAuth-based 'public connections' that undergo a security review before being listed, plus internal connections and webhooks for automations, supporting third-party integration capability. However, there is no evidence pack confirmation of marketplace scale (e.g., 'thousands' of listed integrations), and an older community comment notes a lack of a native GitHub integration, suggesting coverage gaps for some popular tools. Missing for 10: quantitative evidence of marketplace size/breadth, and resolution of specific integration gaps raised by users.
- [claimed-docs] “Public connections use OAuth 2.0 for authentication... Public connections must undergo a Notion security review before being listed on the M…”
- [claimed-docs] “Public connections use OAuth 2.0 for authentication. At creation time, you choose their installation scope”
- [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
- [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
- [community] “Why does Notion not have a GitHub integration? Kind of a dealbreaker for using it on any tech team unless you just want a wiki.”
Extensibility
designerBuild custom views and dashboard widgets that feel native to the product
weight 1 · round drawnLinearnone0/10Evidence only shows saved/shareable filtered views (linear-docs-13) and standard issue/project views — there is no SDK, embed framework, or dashboard-widget builder that would let a designer create custom native-feeling widgets or dashboards. The public API/webhooks/SDK docs (linear-docs-49-53) are developer-facing data access, not a UI customization surface for designers.
Notionnone0/10Evidence shows Notion's API/integrations let developers sync data, automate workflows, and embed third-party content (Tableau, Mixpanel, Canva) inside pages, but there is no documentation of a widget/dashboard SDK or custom-view framework that lets a designer build native-feeling UI components inside Notion itself — embeds are pre-built partner integrations, not designer-authored native widgets.
- [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
- [claimed-docs] “View Tableau charts and dashboards in Notion”
- [claimed-docs] “View Mixpanel boards, reports and charts inside Notion”
- [claimed-docs] “View and share Canva designs in Notion”
Onboarding — getting started and time-to-first-value storiesOnboarding
Getting started and time-to-first-value stories
Getting started
product managerThat exporting my workspace preserves full history—comments, attachments, and audit trails—not just task titles
weight 3 · round drawnLinearnone0/10The evidence pack contains no mention of a workspace export feature at all—only import tooling (from other services into Linear) is documented, with nothing about exporting comments, attachments, or audit trails out of Linear. This is a fair question for a project-management tool, so absence of evidence means 'none' rather than 'na'.
- [claimed-docs] “Import data from other services into Linear”
- [claimed-docs] “Import tooling for uploading from other systems”
Notionnone0/10The evidence pack contains no documentation or claims about Notion's workspace export feature preserving comments, attachments, or audit trails; the only tangential comment (notion-comm-16) suggests users find it 'hard to get stuff out' of Notion, which does not support the story. Missing for 10: any vendor documentation of an export function, evidence of comment/attachment preservation on export, or evidence of audit-trail export.
- [community] “I've started using notion as a kind of personal wiki... My only issue with Notion is that I feel it's hard to get stuff out of it, especiall…”
engineerFollow a guided walkthrough to set up my workspace the first time
weight 1 · round drawnLinearnone0/10No evidence describes an onboarding wizard, guided workspace setup, or first-run tutorial for new engineers; the pack covers agents, integrations, API docs, and changelog features but nothing about initial workspace configuration guidance.
Notionnone0/10The evidence pack contains developer API/MCP documentation and community sentiment, but no mention of an in-product guided walkthrough or onboarding wizard for setting up a workspace for the first time. The closest item (notion-docs-11) is a quickstart for making an API request, not a workspace setup walkthrough, so it doesn't count as evidence for this specific onboarding story.
product managerImport my data from another tool when switching over
weight 2 · round to LinearLinear documents explicit import capabilities: generic 'Import data from other services into Linear' plus a dedicated Jira migration flow ('Smoothly transition from Jira to Linear') and import tooling for uploading from other systems mentioned in the repo README. This directly satisfies the PM's need to migrate data when switching tools, though detail is thin — missing for 10: specifics on which tools/formats are supported, what data (comments, attachments, custom fields) is preserved, and independent/community confirmation that migrations work smoothly in practice.
- [claimed-docs] “Import data from other services into Linear”
- [claimed-docs] “Import tooling for uploading from other systems”
- [claimed-docs] “Smoothly transition from Jira to Linear”
Notionnone0/10The evidence pack covers Notion's REST API, integrations (GitHub, Loom, Tableau, etc.), MCP/agent APIs, and webhook capabilities, but contains no documentation of a native import feature or migration wizard for bringing data over from other tools (e.g., Confluence, Asana, Evernote) during onboarding. Building an import via the API would require custom engineering, not a documented PM-facing onboarding capability.
product managerJumpstart a new project using pre-built templates
weight 2 · round drawnLinearnone0/10The evidence pack contains no mention of pre-built project or issue templates for jumpstarting new projects; the closest feature, the 'project composer' with Linear Agent, is AI-assisted drafting rather than a template library. missing for 10: any documentation of a templates gallery, template selection UI, or first-party/community evidence of template-based project creation.
Notionnone0/10The evidence pack contains no mention of Notion's templates or template gallery feature for jumpstarting projects; it focuses entirely on API, integrations, MCP, and community feedback unrelated to templates. Although templates are a well-known Notion capability, this evidence pack provides no documentation or citation supporting it, so per the rules it must be judged 'none' rather than assumed from outside knowledge.
Pricing transparency
product managerWhether my plan enforces a minimum seat count or annual billing commitment before I subscribe
weight 3 · round drawnLinearnone0/10No evidence in the pack addresses pricing plans, seat minimums, or annual billing commitments for Linear's subscription plans; all evidence relates to product features, API, and integrations. Missing for 10: any pricing page or plan documentation disclosing seat minimums, billing cadence, or contract terms.
Notionnone0/10The evidence pack contains no information about Notion's pricing plans, seat minimums, or annual billing commitments — all content covers API, MCP, integrations, and general product sentiment. This is a fair pricing-transparency question for a SaaS product, but no evidence addresses it.
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to LinearLinear's GraphQL API exposes the same schema used internally to build the app, with full introspection, mutations for issues/projects/comments, webhooks, OAuth2/API key auth, and an SDK, covering most core CRUD and workflow operations (linear-docs-49, linear-supp-graphql-introspection, linear-docs-74, linear-docs-92-93). However, several UI-native features (Agent sessions/Loops orchestration nuances, admin spend limits, Okta/SSO provisioning, third-party app approval flows, mobile-specific review UI) are not clearly exposed as API-first operations, and no independent evidence confirms 1:1 parity between UI and API surfaces. missing for 10: explicit documentation/confirmation that all admin/security settings (SSO, spend limits, app approvals) and newer Agent/Loop features are fully API-controllable, plus independent verification of full UI-API parity.
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
- [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
- [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”
- [claimed-docs] “query Issue { issue(id: "BLA-123") { id title description } }”
- [claimed-docs] “const myIssues = await me.assignedIssues();”
- [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
- [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
- [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
Notion's own API docs claim you can 'read, create, and update nearly everything' via REST API, plus OpenAPI spec, webhooks, MCP server, and agent APIs give broad but explicitly non-complete coverage — the vendor's own wording ('nearly everything') signals known gaps versus full UI parity (e.g., view configuration, granular permissions, some formatting/UX-only features). missing for 10: independent verification of true UI/API parity, explicit list of API-unsupported UI features, hands-on confirmation from developers building full-parity integrations.
- [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
- [claimed-docs] “you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more”
- [probe] “PROBE openapi: HTTP 200 at https://developers.notion.com/openapi.json — contains "openapi" key”
- [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
- [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
- [claimed-docs] “Search content in Notion and connected sources. * Read, create, and update Notion content. * Create pages and databases.”
ai-native userExport all of my data in open formats and leave
weight 3 · round to LinearLinear has no documented one-click 'export all data' feature; however, its open GraphQL API (with full schema introspection, SDK, and reasonable rate limits) lets a technical user programmatically pull out all their issues, projects, and comments, which is a de facto exit path. There's no bulk-export or archive format documented, and community confirms no self-hosting option, meaning a full clean 'leave with your data' workflow is not officially supported. missing for 10: a documented bulk/archival export feature (e.g., JSON/CSV dump), official data-portability tooling, and independent confirmation that a full account export actually works.
- [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
- [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
- [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
- [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
- [community] “I couldn't find a mention of it - but is there any plans or ability to self-host? I'm personally not a fan of keeping everything in the clou…”
Notiondisputedcontradicted4/10Notion's REST API (notion-docs-1, notion-docs-11) lets you read/create/update 'nearly everything' via personal access tokens, which could support scripted data extraction, but there is no documented one-click bulk export to open, portable formats in this evidence pack. Community reports directly contradict the 'easy to leave' narrative: users say Notion data is 'hard to get stuff out of it, especially on mobile' and that it is 'tied to its own cloud service' with 'no way to use it as a standalone app storing data locally,' explicitly citing this as a reason to leave/avoid switching. missing for 10: dedicated bulk export-to-open-format documentation (e.g., Markdown/CSV/HTML export), independent verification that exported data is complete and usable outside Notion, confirmation that API access alone suffices for a full data migration.
- [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
- [claimed-docs] “create a personal access token, make your first API request, and see a new page appear in your workspace in under two minutes”
- [community] “I've started using notion as a kind of personal wiki... My only issue with Notion is that I feel it's hard to get stuff out of it, especiall…”
- [community] “If I've understood it right... Notion is tied to its own cloud service for storing information, and there's no way to use it as a standalone…”
ai-native userRead the product's source under an open license
weight 2 · round drawnLinearnone0/10No evidence indicates Linear's application source is published under an open license; the only related item is a stray README reference on GitHub (linear-docs-101) which does not establish an open-source license or full source availability. Linear is a closed, proprietary SaaS product per all other evidence (docs, integrations, community threads about lack of self-hosting).
- [claimed-docs] “Import tooling for uploading from other systems”
- [community] “I couldn't find a mention of it - but is there any plans or ability to self-host? I'm personally not a fan of keeping everything in the clou…”
Notionnone0/10Notion is a closed-source, proprietary SaaS product; the only open-source artifact mentioned is the notion-mcp-server client tool, not Notion's own application source. No evidence anywhere in the pack indicates Notion's core product source is available under an open license.
- [claimed-docs] “If you need to run your own MCP server, the notion-mcp-server package is available as an open-source implementation.”
- [community] “For now I use Notion with the hopes they implement it eventually [offline read-only mode]. I can't consider switching to a self hosted alter…”
- [community] “If I've understood it right... Notion is tied to its own cloud service for storing information, and there's no way to use it as a standalone…”
ai-native userSelf-host the core product
weight 3 · round drawnLinearnone0/10Linear is explicitly a cloud-only SaaS with no self-hosting option; a community Q&A cites a direct Linear response stating 'We unfortunately don't currently have plans to provide self-hosting' (linear-comm-10). No docs anywhere in the evidence pack mention on-prem/self-hosted deployment.
- [community] “I couldn't find a mention of it - but is there any plans or ability to self-host? I'm personally not a fan of keeping everything in the clou…”
Notionnone0/10Notion is a cloud-only SaaS with no self-hosted deployment option; community evidence explicitly confirms it is tied to its own cloud service with no way to run it as a standalone/local app, and users express desire for a self-hosted alternative that doesn't exist.
- [community] “If I've understood it right... Notion is tied to its own cloud service for storing information, and there's no way to use it as a standalone…”
- [community] “For now I use Notion with the hopes they implement it eventually [offline read-only mode]. I can't consider switching to a self hosted alter…”
- [community] “I love Notion but the speed, or rather lack of, is killing me daily. Last Friday I was taking some notes, and suddenly the page refreshed an…”
Planning tracking — planning and tracking work — issues, sprints, boards, statusPlanning tracking
Planning and tracking work — issues, sprints, boards, status
Mobile access
engineerManage my tasks from a full-featured native mobile app without missing desktop functionality
weight 2 · round to LinearDocs show mobile app supports specific engineer workflows like reviewing code diffs and commenting (linear-docs-6) and, as of a recent update, document creation/editing (linear-docs-71), indicating mobile parity is being actively built out rather than already complete. There is no evidence of full task-management parity (e.g., initiatives, project views, filters, admin settings) on mobile, and no independent/community confirmation of a full-featured mobile experience. Missing for 10: comprehensive mobile feature-parity documentation covering all core desktop workflows (initiatives, filters, admin, integrations), and independent user reviews confirming no functionality gaps on mobile.
- [claimed-docs] “Use the Linear mobile app to review code changes, comment on specific lines, and iterate with Linear Agent.”
- [claimed-docs] “Document creation and editing are now available in Linear's iOS and Android apps.”
Notionnone0/10The evidence pack contains no vendor documentation or claims about a native mobile app with desktop-equivalent task management functionality; instead, community reports mention mobile being 'hard to get stuff out of' and citing 'offline/mobile-first' as a gap serious enough to abandon Notion. No positive evidence supports full mobile parity.
- [community] “I've started using notion as a kind of personal wiki... My only issue with Notion is that I feel it's hard to get stuff out of it, especiall…”
- [community] “As a heavy user of both Confluence and Notion... There's a big need in this feature [offline/mobile-first], and something that's best baked …”
- [community] “I love the product, but the login workflow is awful... a randomly-generated one-time code sent to your email address... A side effect of thi…”
Task management
product managerTrack cross-team dependencies to coordinate large launches
weight 2 · round to LinearLinear's initiative feature lets a team be assigned to lead cross-team work with statuses (proposed/canceled) and priority, which supports coordinating large launches (linear-docs-4, linear-docs-14, linear-docs-37, linear-docs-63, linear-docs-76), and project-view subscriptions notify on changes (linear-docs-61). However, there's no explicit evidence of dependency-specific features like blocking/blocked-by issue relations or a dependency graph across teams. missing for 10: explicit issue-to-issue dependency/blocking relation docs, cross-team dependency visualization, hands-on evidence of coordinating a large launch using these features.
- [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work”
- [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside”
- [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside... Priority commu…”
- [claimed-docs] “Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”
- [claimed-docs] “Plan and navigate from idea to launch. Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”
- [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”
Notion is described as a flexible workspace/'system of record' that teams use for project and task tracking (notion-docs-6, notion-comm-11), which could support dependency coordination, but no evidence specifically documents relation/dependency-tracking features, and one community report notes teams 'quickly reach limits' when using Notion as a project/issue tracker for team coordination (notion-comm-6). Missing for 10: explicit documentation of dependency-linking features (e.g., linked databases, relation properties, timeline/Gantt views), cross-team rollup examples, and independent validation that large multi-team launches are successfully coordinated in Notion.
- [claimed-docs] “Bring everything into one system of record.”
- [community] “We use it to keep track of all of our tasks and projects... notifications are still hit or miss... Search still needs some love... I'd love …”
- [community] “Notion is currently a jack of all trades and master of none. We have tried to use it as a wiki, project tracker, issue tracker, CRM & spread…”
product managerCustomize fields and workflow statuses to match my team's process
weight 2 · round to NotionLinearnone0/10The evidence pack contains no vendor documentation describing custom issue fields or configurable workflow statuses for teams; the only relevant community evidence explicitly states Linear lacks the ability to define different issue types or add custom fields, and describes this as a deliberate design choice against Jira-style customization.
Community feedback describes Notion as highly flexible and configurable enough to serve as a project/issue tracker sitting between rigid PM tools like Jira and unstructured wikis, implying customizable fields/workflows, but the evidence pack contains no first-party documentation specifically describing database property types, status fields, or workflow customization features. Missing for 10: official docs on database property/status customization, screenshots or docs of board/status views, and independent hands-on confirmation of building a PM workflow with custom fields.
- [community] “Notion feels like it's got this serious range from individuals up to teams at large enterprises. It's incredibly flexible and configurable..…”
- [community] “Notion is currently a jack of all trades and master of none. We have tried to use it as a wiki, project tracker, issue tracker, CRM & spread…”
- [community] “Glad to see this here, it's a very well-built product that finds the perfect balance between strict JIRA/PM tools and completely unstructure…”
product managerTrack initiatives with status, priority, and an owning team
weight 2 · round to LinearLinear docs show initiatives support status (Proposed/canceled/other statuses), priority, and an owning team assignment ('assign a team to lead an initiative'), directly matching the story. missing for 10: independent hands-on corroboration of the initiative-tracking UI beyond changelog claims.
- [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work”
- [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside”
- [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work and how it contributes to the broad…”
- [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside... Priority commu…”
- [claimed-docs] “initiatives led by private teams are only visible to team members. This creates a secure place for confidential planning, regulated projects…”
Community evidence confirms Notion is used as a project/initiative tracker by teams (comm-6, comm-15, comm-3), consistent with its flexible database model that supports custom fields like status, priority, and owner, but the evidence pack contains no first-party documentation explicitly describing status/priority/owning-team properties, and one community report notes hitting limits when using Notion as a project/issue tracker. Missing for 10: explicit docs on database property types (status, priority, person/team fields), and independent confirmation of scaling well for initiative tracking at team level.
- [community] “Notion is currently a jack of all trades and master of none. We have tried to use it as a wiki, project tracker, issue tracker, CRM & spread…”
- [community] “Glad to see this here, it's a very well-built product that finds the perfect balance between strict JIRA/PM tools and completely unstructure…”
- [community] “Notion feels like it's got this serious range from individuals up to teams at large enterprises. It's incredibly flexible and configurable..…”
- [claimed-docs] “Bring everything into one system of record.”
engineerPlan and manage sprints for agile software development
weight 2 · round drawnEvidence shows Linear supports general agile planning artifacts—issues, priorities, initiatives, roadmaps, and project alignment (linear-docs-76, linear-docs-63, linear-docs-37)—and community comments confirm it functions as a fast issue tracker (linear-comm-1, linear-comm-6). However, the pack contains no direct evidence of Linear's sprint/cycle-specific features (e.g., cycle planning, sprint velocity, burndown, backlog grooming) that would confirm dedicated sprint management. Missing for 10: explicit documentation of Cycles/sprint creation, velocity tracking, sprint retrospectives, and backlog prioritization tools.
- [claimed-docs] “Plan and navigate from idea to launch. Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”
- [claimed-docs] “Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”
- [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside... Priority commu…”
- [community] “We've been using Linear for a couple months. It's kind of like Superhuman in that the primary benefit is hotkeys. Otherwise it is an issue t…”
- [community] “Can't speak for other teams... but we migrated from JIRA to Linear for our small team, and haven't looked back. Just the simple fact that it…”
Notion's flexible databases (notion-docs-6) can be configured into kanban/sprint boards, and its API/automations (notion-docs-1, notion-docs-3) allow custom workflows, but there is no evidence of native agile/sprint-specific features (backlogs, sprint velocity, burndown, sprint ceremonies). Community feedback explicitly notes it hits limits as a project/issue tracker and lacks GitHub integration, a 'dealbreaker' for tech teams (notion-comm-6, notion-comm-7). missing for 10: dedicated sprint planning primitives, native issue/backlog management, engineering tool integrations (e.g., GitHub/CI), independent evidence of successful agile sprint use.
- [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
- [claimed-docs] “Bring everything into one system of record.”
- [claimed-docs] “Connections can subscribe to real-time events — like page updates, property changes, and new comments — via webhooks.”
- [community] “Notion is currently a jack of all trades and master of none. We have tried to use it as a wiki, project tracker, issue tracker, CRM & spread…”
- [community] “Why does Notion not have a GitHub integration? Kind of a dealbreaker for using it on any tech team unless you just want a wiki.”
engineerCreate tasks and assign them to teammates with due dates
weight 3 · round to NotionEvidence confirms issue creation (IssueCreate mutation) and assignment (assignedIssues, agents 'delegated issues through assignment') as core API/product capabilities, implying basic task creation and assignment support, but no evidence pack item explicitly documents setting or displaying due dates on issues. Missing for 10: explicit documentation of a due-date field on issues, UI walkthrough of assigning a task with a due date, and independent confirmation of this specific workflow.
- [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”
- [claimed-docs] “const myIssues = await me.assignedIssues();”
- [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
- [community] “I have used Linear on a couple of my hobby projects and it's a great tool to quickly capture features and bugs. My one gripe... is that the …”
Notion's API and product docs confirm creating/updating database items (tasks) and pages (notion-docs-1, notion-docs-6), and community evidence confirms real-world use as a 'project tracker, issue tracker' (notion-comm-6), which implies task creation with properties like assignee/due date. However, no evidence explicitly documents assignee or due-date properties, notifications for assigned tasks, or a dedicated task-management UI walkthrough. Missing for 10: explicit documentation of person/assignee property, due-date property, and confirmation that assigned teammates get notified.
- [claimed-docs] “With the REST API, you can read, create, and update nearly everything in a workspace — pages, databases, users, comments, and more.”
- [claimed-docs] “Bring everything into one system of record.”
- [community] “Notion is currently a jack of all trades and master of none. We have tried to use it as a wiki, project tracker, issue tracker, CRM & spread…”
engineerBreak work into subtasks and link dependent tasks so blocking order is clear
weight 3 · round drawnLinearnone0/10The evidence pack contains no mention of sub-issues, issue hierarchies, or blocking/blocked-by dependency links—core planning-tracking features one would expect docs to cover for an issue tracker. Nothing here cites Linear's sub-issue or relation functionality, so this applicable axis is unsupported by the given evidence.
Notionnone0/10The evidence pack contains no mention of Notion's sub-tasks, relation properties, or dependency-linking features for tasks/databases; it focuses on API access, integrations, MCP, and unrelated community complaints. Since planning/tracking of dependent tasks is a fair expectation for a workspace tool like Notion, but no evidence substantiates this specific capability, it must be scored as none rather than na.
engineerLog time directly against tasks and projects
weight 2 · round drawnLinearnone0/10No evidence in the pack mentions time tracking, time logging, or timesheet functionality against tasks/projects in Linear; the evidence focuses on issue tracking, agents, coding sessions, and planning features.
Views organization
engineerHow the product performs and whether item caps apply in workspaces with tens of thousands of tasks
weight 2 · round drawnLinearnone0/10No evidence pack item addresses performance benchmarks, scalability limits, or item caps for workspaces with tens of thousands of tasks; community comments only mention general speed vs Jira without scale specifics. This is a fair question for an issue tracker but remains unaddressed here.
Notionnone0/10No first-party documentation addresses workspace scale limits, item/block caps, or performance guarantees for large databases; the evidence pack only contains generic API/marketplace docs and unrelated integration listings. Community reports (notion-comm-4, notion-comm-8, notion-comm-13, notion-comm-17) even describe hitting a hard 1000-block limit and persistent sluggishness/data loss, but these are anecdotal complaints, not an official statement Notion could be shown contradicting, so this doesn't rise to 'disputed' — it simply lacks any vendor evidence of delivering predictable performance at tens-of-thousands-of-tasks scale.
- [community] “I had a really bad experience with Notion, used it for some time, hit some arbitrary 1000 block limit that no matter what I deleted I couldn…”
- [community] “Notion consuming 10-15% CPU while on idle is a deal breaker to me. I wish they'd devote a bit more resources to fix this. (On macOS)”
- [community] “There is something about Notion that makes it feel very well-made and coherent... On the flip side the software is a bit slow to start and u…”
- [community] “I love Notion but the speed, or rather lack of, is killing me daily. Last Friday I was taking some notes, and suddenly the page refreshed an…”
engineerSwitch between board, list, calendar, and timeline views of the same work
weight 2 · round to NotionLinearnone0/10The evidence pack has no mention of board, list, calendar, or timeline views, or of switching between them — only a generic reference to sharing 'any filtered view' via URL, which doesn't establish this specific multi-view capability.
Community evidence only glancingly confirms Notion supports board/kanban and task-list structures (notion-comm-18), but nothing in the evidence pack explicitly documents calendar or timeline views or the ability to switch seamlessly between all four view types on the same dataset. missing for 10: docs/screens showing calendar view, timeline/Gantt view, and the actual view-switching mechanism on one database.
- [community] “Notion could as well [integrate with Mattermost/discord] but they are a slow moving beast with different priorities.”
engineerSave a filtered view of work and share it with a link
weight 2 · round to LinearLinear explicitly documents saving/sharing filtered views: "You can now share any filtered view by copying its URL from your browser, or by pressing ⌘/Ctrl Shift C on desktop" (linear-docs-13), directly matching the story of sharing a filtered work view via link. Missing for 10: independent/hands-on community confirmation of this specific feature beyond the vendor changelog.
- [claimed-docs] “You can now share any filtered view by copying its URL from your browser, or by pressing ⌘/Ctrl Shift C on desktop.”
Notionnone0/10The evidence pack covers Notion's API, MCP, integrations, and community feedback, but contains no mention of database views, filters, or the ability to save/share a filtered view via link. This is an applicable capability for a workspace/planning tool, but no evidence supports it here.
engineerSearch across all tasks, docs, and comments and get fast, accurate results
weight 2 · round to NotionLinearnone0/10The evidence pack contains no documentation or community commentary about a search feature spanning issues, docs, and comments, nor any claims about speed or accuracy of such search — only filtering/view-sharing and speed-of-loading tickets are mentioned, which is a different capability.
Notiondisputedcontradicted5/10Notion advertises workspace-wide search plus AI-powered 'Get answers, instantly—with citations' and MCP search across Notion and connected sources, but a hands-on team user managing tasks/projects explicitly reports 'Search still needs some love,' directly contradicting the fast/accurate claim. missing for 10: independent benchmarking of search speed/accuracy across large workspaces, resolution of the community complaint, and evidence of comments-specific search quality.
- [claimed-docs] “Get answers, instantly—with citations.”
- [claimed-docs] “Search content in Notion and connected sources. * Read, create, and update Notion content. * Create pages and databases.”
- [community] “We use it to keep track of all of our tasks and projects... notifications are still hit or miss... Search still needs some love... I'd love …”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnLinearnone0/10No evidence in the pack mentions data residency, region selection, or storage location controls for Linear workspaces; only unrelated features (access control via Okta, admin app approvals, self-hosting explicitly denied) are covered.
- [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions. Admins can manage access centrally”
- [community] “I couldn't find a mention of it - but is there any plans or ability to self-host? I'm personally not a fan of keeping everything in the clou…”
Notionnone0/10No evidence in the pack addresses data residency, regional storage options, or geographic control over where workspace data resides; one community comment even notes Notion is tied to its own cloud with no local storage option. This is a fair question for a SaaS platform storing user data, so it applies, but nothing supports it. missing for 10: any mention of region selection, data residency guarantees, EU/US data center choice, or compliance documentation on data locality.
- [community] “If I've understood it right... Notion is tied to its own cloud service for storing information, and there's no way to use it as a standalone…”
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnLinearnone0/10No evidence in the pack addresses AI training data opt-out or any policy preventing customer data from being used to train AI models; the pack covers agents, integrations, API, and workspace features but is silent on AI training data usage policy.
ai-native userControl data retention and deletion
weight 2 · round drawnLinearnone0/10The evidence pack covers admin access control, identity management (Okta/SSO), API rate limits, and agent behavior, but contains no mention of data retention policies, data deletion controls, or configurable retention windows for AI-generated content or session data. Missing for 10: any documentation of retention periods, deletion/export APIs, or admin controls specifically for purging AI agent data or session history.
Notionnone0/10No evidence pack items address data retention policies, deletion controls, export/purge tools, or data lifecycle management for AI-native usage; the pack covers API access, integrations, and MCP but nothing about retention/deletion settings. missing for 10: documentation on data retention policies, deletion/purge controls, workspace data lifecycle settings, AI training data retention/opt-out specifics.
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnLinearnone0/10No evidence in the pack addresses telemetry or usage-tracking opt-out settings for Linear; the material covers agents, integrations, API, and product features but nothing about privacy/telemetry controls. Missing for 10: any documentation of a telemetry setting, opt-out toggle, privacy policy statement, or usage-tracking disclosure.
Notionnone0/10No documentation or feature in the evidence pack describes a telemetry/usage-tracking opt-out control; the only related signal is a community complaint that Notion embeds undisclosed session-recording (FullStory) tracking, which points the opposite direction from a user-facing opt-out.
- [community] “I mentioned this before. Notion is great, but the fact that they use fullstory (session recording) for a note taking app is a huge problem f…”
Reporting insights — stories about reporting insights in this arenaReporting insights
Stories about reporting insights in this arena
Ai insights
ai-native userAsk AI a question and get an instant answer with citations from my workspace content
weight 2 · round to NotionLinearnone0/10The evidence shows Linear Agent can draft updates by gathering context (e.g. 'Write with Agent' reviewing changes and Slack messages) and supports MCP integrations for external AI tools, but there is no documented feature where a user can directly ask a question and receive an instant answer with citations pulled from workspace content. This is a plausible axis for a workspace tool, but no such Q&A/citation feature is evidenced.
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
- [claimed-docs] “Connect ChatGPT deep research to Linear”
- [claimed-docs] “Previews of Linear issues, views and projects and query Notion AI”
Notion's marketing explicitly claims 'Get answers, instantly—with citations' and 'Keep work moving 24/7 with agents,' indicating a Q&A-with-citations AI feature exists, and agent/search APIs (search across Notion and connected sources, agent session APIs) support this. However, there is no detailed documentation, screenshots, or independent/hands-on corroboration showing the citation UX in practice, only marketing taglines and adjacent API references. Missing for 10: hands-on or third-party verification of the Q&A citation experience, detailed docs on how citations are sourced/displayed, and independent confirmation of accuracy/reliability.
- [claimed-docs] “Get answers, instantly—with citations.”
- [claimed-docs] “Keep work moving 24/7 with agents.”
- [claimed-docs] “Search content in Notion and connected sources. * Read, create, and update Notion content. * Create pages and databases.”
- [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
ai-native userHave AI draft a project or initiative status update from recent activity
weight 2 · round to LinearLinear's 'Write with Agent' feature explicitly drafts project status updates by reviewing recent activity changes and linked Slack messages, and Loops can also react to initiative/project changes to keep documents and plans updated automatically. Missing for 10: independent/hands-on corroboration of update quality, and explicit first-party example of initiative-level (vs project-level) status update drafting.
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
- [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
- [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
- [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
- [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
- [claimed-docs] “You can now edit text with Linear Agent, and use Loops to keep docs and project descriptions up-to-date. Author name indicators let you chec…”
Notion advertises AI capabilities like Q&A with citations and always-on agents that work across the workspace (notion-docs-7, notion-docs-8), and its Agent APIs let a Custom Agent read/act on workspace content via sessions (notion-docs-21, notion-docs-22), which could plausibly be used to draft a status update from recent activity. However, there is no concrete documentation or example specifically showing AI generating a project/initiative status update from recent activity — missing for 10: a documented status-update/report-drafting workflow, example prompts/templates, or independent evidence that this specific reporting use case works in practice.
- [claimed-docs] “Get answers, instantly—with citations.”
- [claimed-docs] “Keep work moving 24/7 with agents.”
- [claimed-docs] “Use sessions to start a chat, stream the Agent's reply, submit an action when needed, and read its event history.”
- [claimed-docs] “Find the Custom Agents your token can access, track their usage, and manage their status and credit limits.”
- [claimed-docs] “Bring everything into one system of record.”
Dashboards
product managerBuild dashboards and widgets to report on project progress
weight 2 · round drawnLinearnone0/10The evidence pack covers Linear's agent/AI coding features, initiatives, teams, and API/webhooks extensively, but contains no mention of dashboard-building or configurable reporting widgets for tracking project progress. Filtered/shared views (linear-docs-13) and project view event subscriptions (linear-docs-61) are the closest hints, but neither describes a dashboard or widget system a PM could assemble for progress reporting.
- [claimed-docs] “You can now share any filtered view by copying its URL from your browser, or by pressing ⌘/Ctrl Shift C on desktop.”
- [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”
- [community] “The killer missing feature for us is that we can't define different issue types... there's no way to show the issue layout as an expandable …”
Notionnone0/10The evidence pack covers Notion's API, developer tooling, and general workspace flexibility, but contains no documentation or mention of dashboard/widget-building features for tracking project progress; one community comment even notes Notion 'quickly reach[es] limits of what is possible automatically' when used for project tracking. Missing for 10: any first-party docs on dashboard/reporting widgets, rollups/charts for progress tracking, or hands-on evidence of PMs building such dashboards.
- [community] “Notion is currently a jack of all trades and master of none. We have tried to use it as a wiki, project tracker, issue tracker, CRM & spread…”
product managerRoll up progress across multiple projects into a single portfolio view
weight 2 · round to LinearLinear's Initiatives feature (grouping multiple projects under a lead team, with status like proposed/canceled and priority) points toward portfolio-style organization, but the evidence never explicitly describes progress roll-up (e.g., aggregated completion percentages or a dedicated portfolio dashboard) across projects. Missing for 10: explicit documentation of progress aggregation/visualization across projects, independent/hands-on confirmation of a portfolio view, and any reporting-specific UI details beyond initiative metadata.
- [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work”
- [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work and how it contributes to the broad…”
- [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside”
- [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside... Priority commu…”
- [claimed-docs] “initiatives led by private teams are only visible to team members. This creates a secure place for confidential planning, regulated projects…”
- [claimed-docs] “Plan and navigate from idea to launch. Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”
Notion is broadly marketed as a flexible system of record and used by teams for project tracking (notion-docs-6, notion-comm-3), but no evidence describes rollup properties, portfolio dashboards, or cross-project progress aggregation specifically, and community feedback notes real limits when using Notion as a project tracker. Missing for 10: explicit documentation of rollup/aggregation properties, portfolio-view templates, or dashboard features summarizing multiple projects' progress, and hands-on confirmation this works at scale.
- [claimed-docs] “Bring everything into one system of record.”
- [community] “Notion feels like it's got this serious range from individuals up to teams at large enterprises. It's incredibly flexible and configurable..…”
- [community] “Notion is currently a jack of all trades and master of none. We have tried to use it as a wiki, project tracker, issue tracker, CRM & spread…”
Security — security posture and hardening storiesSecurity
Security posture and hardening stories
Access control
product managerReview an admin audit log of actions taken across the workspace
weight 2 · round drawnLinearnone0/10The evidence pack contains no mention of an admin audit log feature listing actions taken across the workspace; the only near-miss reference (linear-docs-59) discusses private teams enabling 'audits' as a use case, not an actual audit log capability. This is an applicable security/compliance axis for a workspace tool like Linear, but no evidence shows it delivers the capability.
product managerAssign granular permissions and roles to control who can view or edit work
weight 2 · round to LinearLinear offers some access-control building blocks—private/restricted sub-teams and initiatives that limit visibility to team members (linear-docs-15, linear-docs-29, linear-docs-40, linear-docs-59), Okta-based identity and 'existing Linear permissions' management (linear-docs-5, linear-docs-60, linear-docs-67), and admin approval of third-party apps (linear-docs-73)—but there's no evidence of granular, role-based view/edit permission assignment at the issue or field level that a PM could configure themselves. Missing for 10: documented custom roles/permission levels, per-user or per-field view/edit controls, and any PM-facing UI for assigning such permissions beyond team membership.
- [claimed-docs] “Private sub-teams organize groups that work together under one umbrella, like independent business units, skunkworks efforts, or teams handl…”
- [claimed-docs] “For work that requires tighter access, initiatives led by private teams are only visible to team members.”
- [claimed-docs] “Restricted to parent team members — parent team members can see and choose to join the sub-team... Private to team members — the team is hid…”
- [claimed-docs] “initiatives led by private teams are only visible to team members. This creates a secure place for confidential planning, regulated projects…”
- [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions.”
- [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions. Admins can manage access centrally”
- [claimed-docs] “Linear's MCP now supports managing employee access through your existing Okta-managed identity.”
- [claimed-docs] “Third-party app approvals are now available on paid Linear plans, allowing admins to review and approve apps before they're installed.”
Notionnone0/10The evidence pack covers API/OAuth scopes, webhooks, and MCP connection access controls, but contains no documentation of Notion's actual workspace member roles, page/database-level sharing or edit/view permission settings that a product manager would use to control who can view or edit content. notion-docs-30 only mentions managing MCP client connection access, not user role-based content permissions.
- [claimed-docs] “Workspace owners can manage MCP client access in Settings → Connections.”
- [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token. They're ideal for custom automations and workflows”
- [claimed-docs] “Internal connections are scoped to a single workspace and use a static API token.”
product managerCreate private sub-teams restricted to specific members
weight 1 · round to LinearLinear's docs explicitly describe private sub-teams with restricted visibility options — 'Private to team members — the team is hidden, except to members directly invited to that sub-team' and 'Restricted to parent team members', directly matching the story of PM-created private sub-teams limited to specific members. Additional docs confirm these sub-teams can organize sensitive-data groups and that initiatives led by private teams stay confidential. Missing for 10: independent/hands-on corroboration beyond vendor docs.
- [claimed-docs] “Private sub-teams organize groups that work together under one umbrella, like independent business units, skunkworks efforts, or teams handl…”
- [claimed-docs] “Restricted to parent team members — parent team members can see and choose to join the sub-team... Private to team members — the team is hid…”
- [claimed-docs] “For work that requires tighter access, initiatives led by private teams are only visible to team members.”
- [claimed-docs] “initiatives led by private teams are only visible to team members. This creates a secure place for confidential planning, regulated projects…”
engineerSecure organization access with SSO and SAML
weight 3 · round to LinearLinear's docs describe Okta-based identity verification and centralized access management for admins, indicating SSO support, and the MCP changelog confirms managing employee access via Okta-managed identity. However, none of the evidence explicitly mentions SAML configuration or enterprise SSO setup details, and there's no independent/hands-on confirmation of the feature working. Missing for 10: explicit SAML protocol documentation, broader SSO provider support beyond Okta, and independent verification of enforcement.
- [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions.”
- [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions. Admins can manage access centrally”
- [claimed-docs] “Linear's MCP now supports managing employee access through your existing Okta-managed identity.”
- [claimed-docs] “Admins can manage access centrally, without requiring employees to sign in or authorize Linear individually.”
Trust reliability
product managerThe vendor's published uptime SLA and can check real-time incident status via a public status page
weight 3 · round drawnLinearnone0/10No evidence pack item mentions a published uptime SLA or a public status page with real-time incident status; only unrelated docs, community sentiment, and API/agent features are provided. Missing for 10: any mention of an SLA commitment, a status page URL, or incident history/uptime reporting.
product managerThe vendor's documented support response times for each plan tier
weight 2 · round drawnLinearnone0/10No evidence pack item mentions support response time SLAs or plan-tier support commitments; the pack covers product features, API, and agent capabilities but nothing about documented support response times per pricing tier.
Not comparable on these axes
engineerReview AI agent code changes and comment on specific lines from a mobile app, then have the agent iterate
weight 2 · not comparableLinear's docs explicitly state the mobile app supports reviewing code changes, commenting on specific lines, and iterating with Linear Agent (linear-docs-6), backed by broader agent workflow features like Guided Reviews with diff explainers (linear-docs-7), before/after screenshots (linear-docs-27/66), and mobile document editing (linear-docs-71) showing mobile parity investment. Missing for 10: independent/hands-on third-party confirmation of the mobile review-and-iterate flow working smoothly in practice.
- [claimed-docs] “Use the Linear mobile app to review code changes, comment on specific lines, and iterate with Linear Agent.”
- [claimed-docs] “Guided Reviews break diffs into focused sections with explainers on what changed and why.”
- [claimed-docs] “The agent opens the app, navigates through a flow, and verifies its implementation. It also captures before-and-after screenshots”
- [claimed-docs] “It also captures before-and-after screenshots, making visual changes easier to review alongside the code.”
- [claimed-docs] “Document creation and editing are now available in Linear's iOS and Android apps.”
Notionn/aThis story is about reviewing AI coding-agent diffs (code review with inline comments) from a mobile app and having the agent iterate — this is a coding-agent/IDE workflow, not something Notion (a workspace/docs/wiki tool) is built for. Notion's agent features relate to page/content editing, not code diffs or line-level code review.
engineerRestore an AI coding agent's session to any previous checkpoint in its version history
weight 2 · not comparableLinear explicitly documents checkpoint-based version history restore for coding sessions: "If you need to revert to an earlier version, restore to any previous checkpoint from version history" — this directly matches the story of restoring an AI agent's session state. It's first-party documentation only, with no independent/hands-on corroboration of the restore behavior in practice. Missing for 10: independent/hands-on verification of restore reliability, and detail on granularity/scope of what gets restored.
- [claimed-docs] “If you need to revert to an earlier version, restore to any previous checkpoint from version history.”
- [claimed-docs] “Linear Agent can now set up, run, and test your code before returning its work.”
- [claimed-docs] “Coding sessions run in the cloud, so you can prototype ideas and make changes without setting up a local development environment.”
ai-native userHave a coding agent auto-detect and install the toolchains and dependencies it needs for a task
weight 2 · not comparableLinear's docs explicitly state its coding agent detects and installs toolchains/dependencies during a session, plus can pin runtime versions and add setup scripts, and runs in cloud sandboxes without local environment setup. This is direct first-party evidence of the exact capability described, though missing for 10: independent/hands-on verification of this specific auto-detect behavior beyond vendor changelog claims.
- [claimed-docs] “Linear detects and installs the toolchains and dependencies it needs to complete the task.”
- [claimed-docs] “During a session, Linear detects and installs the toolchains and dependencies it needs to complete the task.”
- [claimed-docs] “Teams can go further by pinning runtime versions, adding setup scripts, and defining environment variables.”
- [claimed-docs] “Coding sessions run in the cloud, so you can prototype ideas and make changes without setting up a local development environment.”
ai-native userHave an agent verify its own implementation by navigating the app and capturing before-and-after screenshots
weight 2 · not comparableLinear's own changelog explicitly documents that its coding agent opens the app, navigates a flow, verifies its implementation, and captures before-and-after screenshots for visual review alongside code (linear-docs-27, linear-docs-66, linear-docs-57, linear-docs-25). This directly matches the story's requirement of an agent verifying its own implementation via app navigation and screenshot capture. Missing for 10: independent/hands-on corroboration beyond vendor changelog and no detail on failure/edge-case handling of this verification flow.
- [claimed-docs] “The agent opens the app, navigates through a flow, and verifies its implementation. It also captures before-and-after screenshots”
- [claimed-docs] “It also captures before-and-after screenshots, making visual changes easier to review alongside the code.”
- [claimed-docs] “Once the application is running, Linear Agent tests its work where users experience it: in the browser.”
- [claimed-docs] “Linear Agent can now set up, run, and test your code before returning its work.”
- [claimed-docs] “The agent opens the app, navigates through a flow, and verifies its implementation.”
Notionn/aNotion is a workspace/docs product with an API, agents, and MCP integration for content operations — it has no browser/app UI automation or screenshot-capture capability, so verifying implementation via navigating an app and capturing before/after screenshots is a category mismatch (this axis fits coding/browser-agent tools, not Notion).
engineerHave AI break a code diff into focused sections with explanations of what changed and why
weight 2 · not comparableLinear's 'Guided Reviews' explicitly break diffs into focused sections with explainers on what changed and why, directly matching the story, and this is paired with broader Linear Agent coding-session features (before/after screenshots, mobile review, code review workflows) that support engineers reviewing AI-generated diffs. Missing for 10: independent/hands-on corroboration beyond vendor changelog, and no detail on how granular or customizable the 'sections' are.
- [claimed-docs] “Guided Reviews break diffs into focused sections with explainers on what changed and why.”
- [claimed-docs] “Use the Linear mobile app to review code changes, comment on specific lines, and iterate with Linear Agent.”
- [claimed-docs] “It also captures before-and-after screenshots, making visual changes easier to review alongside the code.”
- [claimed-docs] “Images, fonts, Markdown, and PDFs now render directly inside Linear diffs.”
ai-native userTest against a sandbox environment without touching production data
weight 1 · not comparableLinearn/aLinear is a project/issue-tracking and agent-orchestration tool, not a data platform or database with a production/test-data split; 'sandbox vs production data' is a category mismatch for this product type. No evidence suggests Linear offers sandbox environments for testing against non-production data copies.
designerCollaborate visually with my team on a shared whiteboard
weight 2 · not comparableLinearn/aLinear is an issue tracker/project management and AI-agent workflow tool; a shared visual whiteboard for design collaboration is entirely outside its product category and not offered even tangentially in the evidence.
Notionn/aNotion is a docs/wiki/database workspace with API and integration features; no evidence pack item mentions a visual whiteboard/canvas collaboration feature, and this is a fundamentally different product category (visual whiteboarding tools) rather than something a workspace/API product would ship as an axis.
engineerRequire AI-authored commits to be cryptographically signed with my SSH or GPG key
weight 2 · not comparableLinear's changelog explicitly states coding sessions support signed commits with SSH or GPG keys added in Settings, directly matching the story. missing for 10: no independent/hands-on corroboration confirming enforcement behavior (e.g., that unsigned commits are blocked) or admin-level requirement/policy controls.
- [claimed-docs] “Coding sessions now support signed commits. Add your SSH or GPG key in Settings to enable signing.”